Trigger post-processing workflows after moving AEM Assets
Post-processing workflows in Adobe Experience Manager (AEM) Assets might not automatically trigger when assets are moved using JCR-level operations. Use one of several supported methods to ensure workflows are executed after a move.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions)
Issue/Symptoms
After you move assets in bulk from one folder to another using javax.jcr.Session.move(), post-processing workflows configured as Auto-start on the destination folder do not consistently retrigger. Some assets are processed as expected, while others remain in their previous workflow state until manually reprocessed. This issue is more noticeable with large batches of assets.
Cause
A JCR-level move operation (such as session.move()) doesn’t generate the repository events required for AEM to evaluate and invoke the destination folder’s Auto-start Workflow. As a result, post-processing workflows aren’t reliably retriggered after asset moves unless you use one of the following supported mechanisms.
Resolution resolution
Complete the following steps:
- Select the moved assets in the AEM Assets UI, then select Reprocess Assets from the toolbar or context menu to trigger the post-processing workflow.
- Configure a Workflow Launcher on the destination folder to listen for the appropriate repository modification event (such as Modified) generated by the move operation, and start the post-processing workflow explicitly. Set the launcher to trigger on the correct event type and path.
- If you use a Custom Workflow Runner Service, review its configuration to confirm it handles moved assets, since Auto-start Workflows alone don’t cover this scenario.
- After you implement one of the preceding solutions, verify that the post-processing workflow triggers for assets after they’re moved by checking the workflow status or logs for the affected assets.