Efficiently reprocess bulk video assets for HLS/DASH in AEM Dynamic Media
Reprocessing video assets for HLS/DASH streaming in AEM Dynamic Media can overload the system and cause failures when done in bulk. To ensure smooth operations, process videos in small batches, apply encoding profiles, and use the AEM Assets HTTP API to identify and reprocess failed assets efficiently.
Description description
Environment
Adobe Experience Manager Dynamic Media / Scene7
Issue/Symptoms
- Reprocessing over 2,000 video assets at once in AEM Dynamic Media causes high system load, asset processing failures, and broken website experiences.
- Failed assets require manual identification and individual reprocessing, increasing operational effort.
Resolution resolution
Note: Don’t process all videos at once. Doing so reduces system performance and increases the risk of failures. Process videos in batches with intervals to keep your system stable during bulk operations.
To resolve this issue, follow theses steps:
- Assign a video encoding profile to the folder containing your videos before starting reprocessing.
- Process video assets in smaller batches of about 100 videos at a time, allowing intervals of 2–5 minutes between each batch to prevent excessive server load.
- Use the AEM Assets HTTP API to identify failed or stuck video assets by filtering based on asset state or file status.
- Reprocess only those assets identified as failed or stuck using the same batch approach.
- Verify that all required videos are successfully processed and available for HLS/DASH streaming.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f