AEM AMS Assets - Scene 7 Publish flow | Community
Skip to main content
P
Adobe Champion
P_V_NairAdobe Champion
Adobe Champion
May 24, 2026
Solved

AEM AMS Assets - Scene 7 Publish flow

  • May 24, 2026
  • 1 reply
  • 22 views

Hi ,  looking for guidance on a Scene7 + asset publish flow.
We have a custom workflow where:
We programmatically trigger the Scene7 workflow to generate renditions.Once processing appears complete, we publish the asset.After publish, we call an API on the Publish instance to retrieve asset details.Since Scene7 processing is asynchronous, we added an event listener to monitor the Scene7 status as publishComplete , before triggering publish.
However, we are still seeing inconsistent API responses from Publish, which makes us think there may be a timing/replication/indexing/cache gap somewhere in the flow.
One recurring issue we’ve observed:
The asset shows “Publish Complete” status on AuthorBut the same asset appears with “ReprocessStart” status on PublishWe’re trying to understand why this discrepancy occurs and what the recommended integration pattern is for ensuring Scene7 processing is truly complete before publish/API consumption. We have already enabled the OOTB Scene7ActivationJobConsumer configuration with replicateMetadata=true on Author.

How do you reliably determine that Scene7 processing is fully complete and available on Publish?Has anyone implemented a similar flow successfully?Is the recommended approach to extend/override the OOTB Scene7 workflow and add the publish step at the end?Or is there a better pattern using status events, callbacks, polling, or retry logic?Any guidance or best practices would be appreciated. Thanks!

Best answer by P_V_Nair

We finally identified the root cause. We had not customized the OOTB Scene7 workflow, however, Scene7 sync was  enabled on one of the staging folders in AEM. Later in our flow, after moving the asset, we were also triggering the Scene7 workflow programmatically to same assets from staging folder. This caused the asset to be uploaded twice to Scene7, leading to the inconsistency of metadata. We have now disabled the folder sync, and everything is working as expected without any additional event listener or scheduler.

1 reply

P
Adobe Champion
P_V_NairAdobe ChampionAuthorAccepted solution
Adobe Champion
May 26, 2026

We finally identified the root cause. We had not customized the OOTB Scene7 workflow, however, Scene7 sync was  enabled on one of the staging folders in AEM. Later in our flow, after moving the asset, we were also triggering the Scene7 workflow programmatically to same assets from staging folder. This caused the asset to be uploaded twice to Scene7, leading to the inconsistency of metadata. We have now disabled the folder sync, and everything is working as expected without any additional event listener or scheduler.

Terms & ConditionsAccessibility statement

Loading footer...