DAM assets remain in Processing and don’t generate renditions in AEM as a Cloud Service

This article explains how to resolve an issue in Adobe Experience Manager (AEM) as a Cloud Service where assets uploaded to the DAM remain stuck in the Processing state and do not generate renditions, due to an incomplete Adobe I/O Events configuration.

Description description

Environment

Adobe Experience Manager Assets as a Cloud Service

Issue/Symptoms

  • Assets uploaded to a DAM folder remain in the Processing state.
  • AEM doesn’t generate renditions for the uploaded assets.
  • Associated Sling jobs fail.
  • For this error signature, Author logs include messages such as Adobe I/O Events … registration failed: Your Workspace is missing an imsOrgId and EventConsumingJob … No handlers registered with this id (AssetProcessorEventHandler).

Cause

An incomplete Adobe I/O Events Workspace configuration, such as a missing imsOrgId, prevents the AssetProcessorEventHandler from registering. AEM then doesn’t consume asset-processing completion events. The assets remain in the Processing state and renditions aren’t generated.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the Adobe I/O Events Workspace configuration for your AEM environment and verify that all required settings, including the IMS Org ID, are configured correctly.
  2. Ensure that both the event metadata registration and the OSGi event-handler mapping complete successfully.
  3. Check the asynchronous processing queue for items in an error or stuck state, and remove any affected queue items to unblock asset processing.
  4. Restart the affected AEM components or pods to re-register the Adobe I/O Events handler.
  5. After the restart, verify that the AssetProcessorEventHandler is registered successfully.
  6. Reprocess the assets that remain in the Processing state and confirm that renditions are generated successfully.
  7. Upload a test asset to the DAM and verify that it moves out of the Processing state and that renditions are generated as expected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles