-
Suggestion
-
Resolution: Unresolved
-
None
Description:
In some cases, the Jira migration can get stuck or failed due to the heavy load on the migration downstream services. In such cases, customer don't have the visibility on the JCMA migration plan so they can report the issue to support until we see the exception in the migration logs like below:
2025-10-18 17:14:14,353+0000 JCMA-JCMAExecutorService-pool-14-thread-76 ERROR XXXXX 10XXx1xx09xx2 abc 100.16.64.150,40.109.290.199,30.11.03.209,170.11.196.23,50.133.155.120,102.10.5.4 /rest/migration/latest/plan/details/<PlanID> [c.a.j.migration.utils.CompletableFutureUtil] Execution Exception occurred while fetching future
java.util.concurrent.ExecutionException: com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: ....
.
.
Caused by: com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code on executing HTTP POST to https://api-private.atlassian.com/migrations/v2/migration; expected [200, 201], but received 504: {"timestamp":"2025-10-18T17:14:14.342+00:00","path":"/migrations/v2/migration","status":504,"error":"Gateway Timeout","requestId":"451a9b3f-4581069","message":"Response took longer than timeout: PT14S"}
JCMA should handle such errors properly by either resuming the migration or failing/completing it rather than just showing the stuck screen. Additionally, should also report the errors on the migration plan.
Workaround
Retry the migration after some time (30 minutes or so). If the issue persists, contact Atlassian support at: support.atlassian.com