Dynamic Media nodes missing after video asset processing in AEM as a Cloud Service
Learn how to resolve missing Dynamic Media nodes for video assets after processing in AEM as a Cloud Service.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
Symptoms
- After uploading and processing a batch of video assets in AEM as a Cloud Service, some assets don’t have the expected Dynamic Media nodes or metadata properties (such as
dam:scene7ID) under their asset paths. - This issue typically affects only a subset of assets, while others process as expected.
- The absence of these nodes prevents Dynamic Media features from functioning correctly for the affected assets.
Resolution resolution
Follow the steps below to resolve the issue:
-
Identify the affected assets:
- Use the AEM Query Debugger or a similar tool to search for assets missing the Dynamic Media metadata. For example, run a query for assets under your DAM path (such as
/content/dam/your-folder/) that don’t have thedam:scene7IDproperty.
- Use the AEM Query Debugger or a similar tool to search for assets missing the Dynamic Media metadata. For example, run a query for assets under your DAM path (such as
-
Review processing logs:
- Check the Dynamic Media processing logs in AEM for any errors or incomplete processing events related to the affected assets.
-
Reprocess the affected assets:
-
In the AEM Assets UI, select the assets missing Dynamic Media nodes.
-
Use the Reprocess Asset option, or trigger the appropriate workflow to re-initiate Dynamic Media processing for these assets.
-
-
Monitor processing:
- Ensure that the reprocessing completes successfully. You can monitor the status in the AEM Assets UI or by checking the asset properties for the presence of Dynamic Media metadata (such as
dam:scene7ID).
- Ensure that the reprocessing completes successfully. You can monitor the status in the AEM Assets UI or by checking the asset properties for the presence of Dynamic Media metadata (such as
-
Verify resolution:
- Confirm that the previously missing Dynamic Media nodes or metadata are now present for all affected assets.
-
If the issue persists:
- Collect relevant logs and asset details, and contact Adobe Support for further assistance.
recommendation-more-help
experience-cloud-kcs-help-kbarticles