ÃÛ¶¹ÊÓƵ

Documentation

Spin Sets stuck in processing state in AEM Dynamic Media

Last update: Fri Jul 04 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In ÃÛ¶¹ÊÓƵ Experience Manager (AEM) as a Cloud Service, Dynamic Media Spin Sets sometimes get stuck in a processing  state and don’t trigger the post-processing workflow automatically. This means you have to manually publish them, which isn’t scalable for large asset volumes. To fix this, you can either switch to Immediate Publish mode or configure a workflow launcher that targets Spin Sets specifically.

Description description

Environment

ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS) - Assets

Issue/Symptoms

When using batch set functionality or node.js binary upload library for asset ingestion, you encounter the following:

  • Spin Sets remain in a processing  state indefinitely.
  • Post-processing workflows don’t trigger automatically.
  • Manual publishing clears the status but isn’t scalable.
  • Workflow launchers cause conflicts or loops if misconfigured.

Resolution resolution

  1. Go to your Dynamic Media settings and change the publish mode from Upon Activation to Immediate Publish. This ensures assets are published right after processing, without needing a post-processing workflow.

  2. Create a workflow launcher that targets Spin Set assets. Configure the workflow launcher with the following settings:

    • Event type: Resource Created and/or Resource Modified

    • Node type: dam:Asset

    • Conditions:

      code language-none 
      jcr:content/dam:s7damType == SpinSet
jcr:content/dam:lastS7SyncStatus == success
jcr:content/metadata/dam:scene7ID != ""
      • Exclude list:
      code language-none 
      (.*)dam:scene7((?!ID).*),
(.*)jcr:content/related(/((?!/sling:members/sling:resources).)*),
(.*)cq:lastReplicat(.*),
(.*)cq:isDelivered,
(.*)jcr:created(.*),
(.*)jcr:lastModified(.*)

      Link this launcher to a workflow model that includes tree activation steps for publishing.

  3. If automation isn’t in place yet, manually publish Spin Sets after creation to clear the processing status.

Note: By design, AEM doesn’t automatically run post-processing workflows for asset sets like Spin Sets. That’s why they stay in a processing  state unless manually published. To automate this, you’ll need to set up a workflow launcher that specifically targets Spin Sets when they’re created or modified. Make sure to configure it carefully so it only triggers when needed and doesn’t run multiple times for the same event.

  • Spin Sets in AEM as a Cloud Service User Guide
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f