Asset reprocess workflow and reupload workflow behaving differently? | Community
Skip to main content
Vishal_Anand
Vishal_Anand
Level 5
February 25, 2026
Solved

Asset reprocess workflow and reupload workflow behaving differently?

  • February 25, 2026
  • 5 replies
  • 55 views

Hi,

We are facing weird issue where video when successfully reprocessed isn’t loading when played via DASH delivery (Video.js player) but works fine when triggered via re-upload workflow. Has anyone encountered this issue? We checked with Adobe support team but haven’t heard back on the root cause of this.

    Best answer by Vishal_Anand

    Adobe’s recommendation:

    POST call to /bin/asynccomand with:

    Operation=PROCESS
    ProcessType=full
     

    Is enough to trigger the DM processing and status update. We can explicitly set FileStatus as NeedsReupload to trigger Reupload workflow if we see seeing obsolete video manifest files or renditions after video upload/ reprocessing. 

    "dam:scene7FileStatus=NeedsReupload"

    No explicit root cause identified from Adobe for the issue except the captured obsolete renditions or Videos being published prior processing was completed. 

    Note: Once video is uploaded, if content admin is not in card view, they will not know if processing is complete. If they trigger Quick publish or Manage publication, it creates issues with video not available for DM server to render on the UI.

     

     

    5 replies

    giuseppebaglio
    giuseppebaglio
    Level 10
    February 26, 2026

    hi ​@Vishal_Anand,

    I don’t have firsthand experience with this issue, but could you review those articles about HLS/DASH in AEM Dynamic Media to see if they offer any guidance?:

    DASH/HLS adaptive streaming returns “Advanced Streaming is not enabled” error in AEM Dynamic Media

    Efficiently reprocess bulk video assets for HLS/DASH in AEM Dynamic Media

    Vishal_Anand
    Vishal_AnandAuthor
    Level 5
    February 27, 2026

    Thanks for the response ​@giuseppebaglio . I did go through these documentation. It seems to be tied to product issue. I am working closely with Adobe engineering team on this.

    giuseppebaglio
    giuseppebaglio
    Level 10
    March 3, 2026

    If possible, please include the Adobe internal ticket ID here – this will be helpful for future reference should a similar issue arise.

    PGURUKRISHNA
    PGURUKRISHNA
    Level 4
    March 2, 2026

    Hey ​@Vishal_Anand 

    Reprocess workflow doesn't clear existing DASH renditions/manifests, causing conflicts. Re-upload does a full cleanup first.

    Fix:

    Manually delete video renditions before reprocessing, or modify your reprocess workflow to include a rendition cleanup step that removes 

    .mpd

     files and video renditions before regenerating them.

    The root cause is stale/conflicting DASH manifest files that reprocess doesn't remove but re-upload does.

      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity Advisor
      Community Advisor
      March 2, 2026

      Hi ​@Vishal_Anand ,
      Root cause: Reprocess does not delete existing DASH renditions/.mpd manifests, so old + new streaming artifacts conflict. Re‑upload does a full cleanup first, so it works.
      try: 

      • Before reprocessing, delete all video renditions and .mpd (and related HLS) files for the asset.
      • Or add a custom cleanup step in your reprocess workflow to do this automatically, then let Dynamic Media regenerate renditions.

      That makes reprocess behave like re‑upload for DASH playback.

      Thanks,
      Amit

      Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
        Vishal_Anand
        Vishal_AnandAuthor
        Level 5
        March 3, 2026

        ​@AmitVishwakarma  Not sure if that is the case since videos which were uploaded in 2024 (without DASH manifest) are also not working post re-processing and it required re-upload workflow to make it functional.

        raf-winterpacht
        raf-winterpacht
        Level 3
        March 2, 2026

        ​@Vishal_Anand this sounds like a very interesting discrepancy, and I’m curious to hear what Adobe comes back with. Have you been able to review logs with DEBUG levels, and see if that gives some clues for the differences in processing? I imagine that should give some clues.

        Raf Winterpacht - Adobe SME, Adobe Professional, Adobe Expert
        JimPresley
        JimPresley
        Level 2
        March 3, 2026

        Something to check too.   We have a similar issue.  We have AEMaaCS and Workfront connected via Adobe cloud native connector.  When the video file is dropped into a linked AEM Assets viewable folder in Workfront, when the asset is passed to AEM it never publishes to Dynamic Media due to an incorrect mime-type reported on ingest. Since it is not reported as a video, it never gets procesed as media.   If a re-process workflow is run on AEM, it publishes fine to DM and then plays/deploys correctly.  Still looking into why the incorrect mime-type is passed when syncing from WF.

          Vishal_Anand
          Vishal_AnandAuthorAccepted solution
          Level 5
          March 10, 2026

          Adobe’s recommendation:

          POST call to /bin/asynccomand with:

          Operation=PROCESS
          ProcessType=full
           

          Is enough to trigger the DM processing and status update. We can explicitly set FileStatus as NeedsReupload to trigger Reupload workflow if we see seeing obsolete video manifest files or renditions after video upload/ reprocessing. 

          "dam:scene7FileStatus=NeedsReupload"

          No explicit root cause identified from Adobe for the issue except the captured obsolete renditions or Videos being published prior processing was completed. 

          Note: Once video is uploaded, if content admin is not in card view, they will not know if processing is complete. If they trigger Quick publish or Manage publication, it creates issues with video not available for DM server to render on the UI.

           

           
            Terms & ConditionsAccessibility statement

            Loading footer...