DocumentationExperience Cloud KCS

AEM as a Cloud Service content copy import fails with QUEUE-102 error

Last update: September 3, 2026

This article explains how to resolve issues where an Adobe Experience Manager (AEM) as a Cloud Service content copy import operation fails with a ‘FAILED’ status due to a QUEUE-102 error, often after importing large content sets over an extended period.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms

  • A content copy (import) operation for a large content set runs for an extended period and ultimately fails.
  • The import job status in the UI is FAILED.
  • Backend logs show that multiple packages import successfully, but the process fails at the final stage.
  • No explicit package import errors appear in the logs, and most packages report successful imports.
  • The Cloud Manager progress bar remains stuck, for example, at 6%, even though backend processing continues.

Cause

The import job fails with a FAILED status because, after a long-running import of a large content set, the system reaches its maximum execution time and is unable to delete a processed message from the queue (QUEUE-102). This causes the overall import to be marked as failed even though most content imports successfully.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the import logs to confirm how many packages imported successfully. Look for messages indicating successful package imports and verify whether the process failed at the final stage.
  2. In the target environment, use the AEM Sites Console to check whether the expected sites and pages exist and whether their content matches the source environment.
  3. Compare representative pages between the source and target environments to confirm content consistency.
  4. To reduce the risk of execution time limits and queue cleanup errors, split large content sets into smaller units and perform multiple, smaller import operations.
  5. Monitor the Cloud Manager progress bar and backend logs during the import. If the progress bar stalls but the logs show continued activity, allow the process to continue while monitoring for potential timeouts.
  6. If the Cloud Manager UI progress remains stuck and no new logs appear, investigate the import operation further.
  7. After completing the above steps, ensure that all intended content has been imported and is accessible in the target environment.

​‌

Content Copy in AEM as a Cloud Service

recommendation-more-help
experience-cloud-kcs-help-kbarticles