Rate this page:
This feature will give users better insight into recent migration activities in descending time order, such as app data uploaded events and updates from your Cloud app. Additionally, it aids in debugging app migration issues by providing warning logs, transferId, and s3Keys. This will be available starting JCMA 1.9.12 and CCMA 3.4.11 onwards.
Not every migration action produces logs, so the absence of events doesn't mean there's no progress, e.g., currently, we do not show logs for when mappings are retrieved.
We recommend providing regular status updates to keep users informed about the progress and to prevent the migration from appearing stuck due to a lack of progress logs.
You can download progress logs on the plan details page by clicking the "View Logs" link. The following image provides a preview of this:
The image below shows an example of a CSV that can be downloaded:
These are expected progress logs that occur during an app migration.
|Logged at the start of the app migration. Use the transfer ID to correlate progress logs with your internal logs.|
|App data has been uploaded to cloud storage. Learn more about retrieving app data|
|Your cloud app has successfully responded to a webhook call.|
|Represents a status update provided by your cloud app. The entry includes up to 500 characters of your message.|
|A customer has requested to cancel a transfer.|
|There are too many log entries to return, so older entries are omitted.|
These logs could impact the success of a migration.
|An uncaught exception has occurred in the server-side listener method (), possibly preventing the execution of further code. This could cause the app migration to ultimately time out.||To avoid a stuck migration, we recommend that your cloud app updates the transfer to a settled status. Refer to server-side-exceptions for more detail.|
|We could not find a webhook to notify your cloud app of the given event, e.g., . Note there is a check run before migration that is related to this warning.||We recommend that your cloud app has added a webhook URL in the connect descriptor while maintaining the registered webhook. The customer should also ensure the cloud site is available with an active license during the migration.|
|Your cloud app failed to return a 200 OK response for a webhook event after multiple retries.||Ensure your cloud app is returning a success response in a timely manner. Read more about webhooks here.|
We have mapped the event types defined here to a more readable message, which is appended to notification-related logs, e.g., .
|start of app migration|
|app data uploaded|
|error in the server app|
|cancel app migration|
Currently, we display up to the most recent 4000 logs. Older logs will be omitted.
Rate this page: