Resolve assets stuck in processing in AEM as a Cloud Service
This article describes how to address an issue in Adobe Experience Manager as a Cloud Service where uploaded assets remain stuck in the processing stage and can’t be published.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Symptoms
- Assets uploaded to the Digital Asset Manager (DAM) remain stuck in the processing stage for an extended period.
- Assets can’t be published or used as expected.
- The issue occurs after heavy system load, such as large numbers of page activations or bulk asset uploads.
- Clearing the workflow queue doesn’t resolve the issue.
- There are no specific error messages in logs or the user interface.
Resolution resolution
Follow the steps below to resolve the issue:
-
Restart the AEM Author service pods:
-
Log in to the Cloud Manager console for your AEM as a Cloud Service environment.
-
Navigate to the Environments section and select the affected environment.
-
Use the available controls to restart the Author service pods. (Refer to your organization’s procedures for restarting services if you don’t have direct access.)
-
-
After the restart, upload a new asset to verify that asset processing completes successfully and that the asset can be published.
-
Monitor Experience League release notes for AEM as a Cloud Service to check for updates or maintenance releases that address asset processing issues. Ensure your environment is updated when a relevant fix is available.