Troubleshoot stuck or failed Content Copy activities in AEM as a Cloud Service
This article explains how to troubleshoot Content Copy activities in Adobe Experience Manager (AEM) as a Cloud Service that become stuck or fail while copying content between environments. An activity can remain in In progress even after the content has been imported successfully. To fix this, review the source and target logs, verify the package import, avoid restarting an activity based only on a delayed status, and retry the operation when content is missing or errors persist.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- Adobe Cloud Manager Content Copy activity
- Source and target environments
Issue/Symptoms
Content Copy activities can fail or remain stuck while copying content between environments. An activity can appear to be in In progress even after the content has been successfully imported because the status update is delayed or incorrect.
- The logs show HTTP status code
404with the message The specified blob does not exist. - Duplicate import jobs appear.
- The activity remains in In progress after the content packages have been imported successfully.
Cause
Possible contributing conditions include intermittent failures while downloading content packages and high load on the target environment. These conditions can delay status updates or trigger duplicate import jobs.
Resolution resolution
Follow these steps to investigate the Content Copy activity and verify whether the content import completed successfully:
-
Review the Content Copy logs in Cloud Manager for both the source and target environments:
- Look for a successful package-import message such as Finished importing content into the destination AEM.
- Check for errors, especially HTTP status code
404with the message The specified blob does not exist.
-
Verify whether all content packages were imported successfully by checking the target environment logs, even if the Content Copy activity appears stuck.
-
If the logs confirm that all content packages were imported successfully and the activity remains in In progress, do not restart the activity based only on its status.
-
If the activity remains stuck and content is missing or errors persist, use the supported cancellation control for the applicable Content Copy flow, if available. After a short wait, initiate a new Content Copy operation.
-
Monitor the new Content Copy activity for progress and review the source and target logs again.
-
If the issue persists after the retry, provide the relevant Content Copy logs and activity details to Adobe Support for further investigation.
Note: Restarting an activity after the content packages have already been imported can trigger duplicate import jobs or cause further delays. Verify the import logs and target content before restarting or retrying the activity.