Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-2358

CCMA migration plan stucks on "Checking for errors" in an endless loop

XMLWordPrintable

    • 5
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      On CCMA migration after we make the selections (spaces, users etc.) it moves to the next screen and enters into an endless loop saying "Checking for errors" and nothing happens. When you click on "View Details" it shows "No errors or warnings" which is the confusing behavior.

      This happens due to the expired authentication token.

      Steps to Reproduce

      1. Create new CCMA migration plan
      2. Select the spaces, users groups, apps and click on next it shows the message "Checking for errors" for longer time without any progress.

      Expected Results

      Migration should move to next stage where it starts the preflight checks else it should show message/warning indicating the expired authentication token instead of running in loop on "Checking for errors"

      Actual Results

      It enters into the endless loop showing "Checking for errors". The below exception is thrown in the migration log file:

      2025-08-15 11:00:00,123 ERROR [http-nio-8090-exec-60 url: /rest/migration/latest/plan; user: abc] [agent.service.catalogue.PlatformService] getAppsProgress Error when trying to get app progress for plan xxxx-xxx-xxxx-xxxx-xxxxxx.
      – url: /rest/migration/latest/plan | userName: abc | referer: https://xyz/admin/migration.action | traceId: 1234567890
      com.atlassian.migration.agent.okhttp.HttpServiceException: Unauthorized
      at com.atlassian.migration.agent.okhttp.ServiceErrorCodeHandler.errorResponseToException(ServiceErrorCodeHandler.java:40)
      

      Workaround

      • Renew the authentication token and wait for 5-10 minutes for the existing migration plan to progress.
      • If the existing migration plan doesn't progress, stop it and create a new migration plan. It should proceed as expected after the renewed token.

              Unassigned Unassigned
              421a2e06c4a8 Jyoti Verma
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: