AEM as a Cloud Service: Assets not moving from placeholder folder despite workflow conditions met
This article addresses an issue where assets remain in a placeholder folder in Adobe Experience Manager as a Cloud Service, even though workflow trigger conditions are satisfied.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
Issue/Symptoms
A large number of assets accumulate in a specific folder (For example: /content/dam/<tenant>/api-pa-placeholder) on the AEM Author instance. The assets display the properties dam:assetState=processed and apiprocessed=true, which should trigger the custom Product API Asset Move Workflow. However, the assets remain in the placeholder folder and aren’t moved to their intended downstream locations.
- No error messages are visible in the UI.
- The issue persists even though the workflow conditions are met for most files.
Cause
The custom workflow configuration or downstream logic didn’t consistently move assets out of the placeholder folder, even when trigger conditions were met. Adjusting the workflow and resolving repository conflicts allowed assets to be processed as intended.
Resolution resolution
Follow the steps below to resolve the issue:
- Review the configuration of the custom ingestion and move workflow, including the Product API Asset Move Workflow and any related workflow launchers.
- Check for repository conflicts or logic errors in the workflow code that could prevent assets from being moved.
- Adjust the workflow configuration and downstream code, as needed, to ensure that assets with
dam:assetState=processedandapiprocessed=trueare processed correctly. - Monitor the placeholder folder to confirm that assets are moving as expected after the changes.
- If the issue persists, review AEM workflow logs for errors or skipped steps, and validate that no repository locks or permission issues are blocking the move operation.