Issue Summary

When data copy is initiated to different sandboxes from the same cloud site around the same time, one of the sandbox data copies might get stuck, never complete or may time out after a few days.

Steps to Reproduce

1. Start parallel data copies to different sandboxes from a single cloud site simultaneously.

Expected Results

The data copy for all sandboxes should be completed successfully as a separate process.

Else, if this is not feasible, the users should get an error/warning message on the UI: "Please let the previous sandbox data copy complete before triggering".

Actual Results

• The sandbox data copy either gets stuck, which may not complete at the end, and shows the following exception in the backend logs: 

Task XXXXX is running with LockKey cloud-export details:TaskProgressImpl{id=XXXXXX, userId=XXXX, description=Cloud Export task, message=Exporting JIRA data, status=RUNNING, progress=XX, submittedTime=... ..., result=null, cancellable=N, lockKey=cloud-export} 

• The sandbox data copy timed out after a certain days  and shows below message in the backend logs:

Found other in progress migrations [MigrationDetailsResponse(migrationId=f0xxxxe-dc97-xxxx-814b-xxxxxxxx, creator=rrr120:abdxxxx-ad33-4310-xxae-xxxxxx7094 

Workaround

• Please trigger only a single data copy from a cloud site and wait for it to complete before initiating another data copy.
• If the data copy is showing as "Copying data" for a longer time than anticipated, please contact Atlassian support to check the status from the backend.