DAM asset subtree not fully published causes redirect flow issues in Adobe Experience Manager
This article explains how incomplete publication of a DAM asset subtree in Adobe Experience Manager (AEM) will lead to issues with redirect flows or dependent pages, and provides steps to ensure all required assets are properly published.
Description description
When publishing a DAM asset or header in AEM, the publication reports as successful even if not all assets within the subtree are fully replicated to the Publish environment. This results in affected flows or pages failing to load correctly, such as redirect flows or other features that depend on these assets. Republishing the affected page alone doesn’t resolve the issue if the underlying DAM assets are missing or incomplete on the Publish instance.
Environment
- Adobe Experience Manager (AEM), all versions
- On-premise or customer-managed deployments
Symptoms
- Redirect flows or pages dependent on DAM assets fail to load or display continuous loading/spinning.
- No explicit error messages in the UI.
- Republishing the affected page doesn’t resolve the issue.
- Service is restored after performing an Activate Tree operation on the DAM asset path.
Cause
The initial publication of the DAM asset reported success but didn’t fully replicate all required assets to the Publish environment. This is often due to incomplete subtree activation or replication inconsistency. Using Activate Tree ensures all assets and dependencies are published.
Resolution resolution
Follow the steps below to resolve the issue:
- Verify that the DAM asset subtree is fully published to all relevant Publish instances.
- Review replication queues for any stuck, failed, or incomplete items related to the affected DAM asset path during the incident window.
- Examine Author and Publish instance logs for errors or warnings related to asset replication or activation at the time of the initial publication.
- When publishing complex or nested DAM assets, use the Activate Tree function to ensure all child assets and dependencies are replicated.
- After publication, verify that all required assets are accessible on the Publish environment by browsing to their URLs or using AEM’s asset browser.
- If the issue recurs, collect detailed Author, Publish, Dispatcher, and Replication logs from the relevant time window for further analysis.
To verify resolution, confirm that the affected flows or pages now load correctly and all required assets are available on the Publish instance.