AEM as a Cloud Service: Resolving assets stuck in processing state

This article explains how to resolve an issue in Adobe Experience Manager as a Cloud Service (AEMaaCS) where newly uploaded assets remain in the processing state and cannot be published or deleted. The solution involves restarting the Author service and reprocessing the affected assets.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)

Issue/Symptoms

  • Assets uploaded to the DAM remain in the Processing state indefinitely.

  • Affected assets cannot be published or deleted.

  • The issue is reproducible by uploading a new asset to the DAM. The asset does not transition to the Processed state.

  • Log entries may include messages such as:

    code language-none
    Found stuck asset '/content/dam/...'
    Received event with type 'rendition_created', asset '/content/dam/...'
    

Cause

A transient fault in the Author service asset-processing queue can cause asset-processing jobs to become stuck, preventing assets from being published or deleted. Restarting the Author service and reprocessing the assets resolves the issue.

Resolution resolution

Follow these steps to resolve the issue:

  1. In Cloud Manager, navigate to the affected environment.
  2. Add a harmless dummy environment variable to the Author service (for example, STUCK_RESTART=1) to trigger a controlled restart of the Author pod or pods.
  3. Wait for the Author pod or pods to restart and return to a healthy state. Monitor the pod and service status in Cloud Manager.
  4. After the restart, sign in to AEM Author and navigate to Tools > Assets > Processing Profiles, or use the DAM UI to locate the assets stuck in the Processing state.
  5. Select the affected assets and choose Reprocess Assets from the toolbar. Process assets in batches of 50 to 100 assets at a time to avoid overloading the processing queue.
  6. Monitor the status of each batch. The assets should transition from Processing to Processed, and renditions should appear.
  7. Confirm that publish and delete operations now work for the reprocessed assets.
  8. As a final verification step, upload a test asset and confirm that it transitions from Processing to Processed within a few minutes.
recommendation-more-help
experience-cloud-kcs-help-kbarticles