Issue Summary

When refreshing Confluence spaces in a sandbox, the system detects if a space already exists. If the user selects "Delete spaces" and confirms, the UI loops back to the "space already exists" screen. Even if the deletion has already occurred in the background, the user must manually restart the copy process. This causes confusion, as it appears the deletion failed, and adds redundant steps to what should be an automated workflow.

Steps to Reproduce

1. Navigate to Admin Hub > Sandboxes.
2. For the Confluence site, click the ellipsis menu (...) and select Copy production data.
3. Choose Specific spaces.
4. Select spaces that already exist in the sandbox.
5. (Optional) Include attachments to increase the processing time.
6. The validation process begins: Validating "Checking for duplicate spaces".
7. The system returns: "Some spaces already exist in your sandbox" (Expected).
8. Click the Delete spaces button.
9. Confirm the action in the "Delete Spaces" pop-up.
10. An asynchronous process starts to delete the spaces. 

Expected Results

A message states that the spaces are being deleted in the background. It advises the user to refresh the space list on Confluence until they are removed and then restart the copy process, returning the user to the initial space selection step.

Actual Results

After confirming the deletion, the UI returns to the same "Validating" page instead of reflecting the updated state.

Since the deletion may still be running in the background, the user has no feedback that anything happened — leading them to assume it failed.

This causes them to trigger the validation again, which surfaces the same duplicate space. The user then attempts to delete it again, creating a loop of repeated actions with no clear resolution.

Workaround

Monitor the availability of the space(s) being deleted and restart the copy process once the spaces have been deleted.