Resolving long queue times and errors for Create Live Copy for Assets jobs
When running Create Live Copy for Assets operations on Content Fragments in AEM as a Cloud Service, jobs remain queued longer than expected or fail with errors indicating the destination fragment already exists. This happens when multiple live copy operations are triggered, or when content-level conflicts prevent successful creation of the destination copy. To fix this, review affected jobs, identify content conflicts, remove or update existing fragments, and re-run the live copy only when required.
Description description
Environment
- Adobe Experience Manager (AEM) as a Cloud Service – Sites
Issue/Symptoms
- Create Live Copy for Assets jobs are shown as Queued for an extended period in Tools *
>General>*Jobs. - Some jobs show Status = Error with messages such as: Job with id: … failed due to: Destination already exists at : /content/dam/…
- Multiple queued and failed
asyncCreateLiveCopyjobs are visible in the Jobs console.
Resolution resolution
Follow these steps to resolve the issue:
-
Go to Tools
>General>Jobs in AEM. -
In the Jobs console, filter for the Create Live Copy for Assets operation or the
asyncCreateLiveCopytopic. -
For each job with Status = Error, open the job details and review the Job Error Log:
-
If the log contains Destination already exists at
<path>:- If the destination fragment is valid and should remain, don’t re-run the Create Live Copy operation for that source‑destination pair. Use rollout or synchronize from the language master to propagate changes.
- If you need to re-seed the locale, delete or move the existing destination fragment at the specified path and then re-run the Create Live Copy for Assets operation.
-
-
After resolving the content conflicts, delete the corresponding error jobs from the Jobs console to keep the job list clear.
-
Avoid starting multiple large Create Live Copy for Assets operations in parallel for the same set of fragments and locales because this increases queue load and delays processing.
-
Verify that new Live Copy jobs complete within the expected timeframe, usually within minutes depending on load and volume.
Notes
- Extended queue times for Create Live Copy for Assets are usually due to normal asynchronous processing under load, not a malfunctioning queue.
- Errors of the form Destination already exists at : /content/dam/… indicate content-level conflicts where the destination node already exists when the async job executes. These conflicts must be resolved before re-running Live Copy creation.