DocumentationExperience Cloud KCS

AEM Assets: Workflow not triggering for title sync on specific assets in Production

Last update: July 31, 2026

This article addresses an issue where a custom workflow for syncing asset titles in Adobe Experience Manager Assets doesn’t trigger for certain assets in the Production environment, despite working in lower environments.

Description description

Environment

Adobe Experience Manager (AEM) as a Cloud Service (all versions)

Issue/Symptoms

A workflow is configured in AEM Assets to synchronize the jcr:title value to dc:title when an asset’s title is updated. In the Production environment, some assets don’t trigger this workflow when their titles are edited, while the same assets copied to a lower environment under the same path trigger the workflow, as expected.

  • The workflow is expected to trigger on title updates via the Assets UI.
  • No workflow instance is observed in Production for the affected assets after updating the title.
  • The issue is asset-specific: only certain assets are affected, not all assets in the same folder or path.
  • No error messages are shown in the UI, but workflow instance logs don’t show any trigger for these assets.

Example asset paths (Production):

  • /content/dam/xxxx/commercial/xxxx/smith/piece/display/static/smith banner 3.png
  • /content/dam/xxxx/commercial/xxxx/smith/piece/direct mail - direct mail/xxxx 2021 V3.html

Steps to Reproduce

  1. In the Production environment, locate an affected asset.
  2. Edit the asset’s title using the Assets UI.
  3. Check the workflow instance logs for any trigger related to the asset.
  4. Observe that no workflow instance is created for the title update.

Additional Notes

  • The same assets, when copied to a lower environment, trigger the workflow, as expected.
  • The workflow launcher is configured for node modification events, typically on jcr:content/metadata.

Cause

The workflow doesn’t trigger because, for certain assets in Production, title updates don’t modify the jcr:content/metadata node that the workflow launcher is configured to watch. This can be due to differences in node structure, missing metadata nodes, or launcher conditions/exclusions that apply only to those assets.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Verify Workflow Launcher Configuration

    • In AEM, navigate to Tools > Workflow > Launchers.
    • Confirm that the workflow launcher is configured to listen for the correct event type (For example: Node Modified) and node type (For example: nt:unstructured) on the expected path (For example: /content/dam/.../jcr:content/metadata).

  2. Compare Node Structures

    • For an affected asset in Production, use CRXDE Lite or a similar tool to inspect the node structure under jcr:content.
    • Check if the metadata node exists and whether the jcr:title property is being updated under jcr:content/metadata or only under jcr:content.
    • Compare this with the same asset in the lower environment where the workflow triggers correctly.

  3. Check Workflow Launcher Conditions and Exclude List

    • Review any conditions or exclude list entries in the workflow launcher configuration (For example: event-user-data:changedByWorkflowProcess).
    • Ensure that no property or user data on the affected assets is causing the launcher to skip triggering.

  4. Enable DEBUG Logging (if further investigation is needed)

    • Use Cloud Manager > Manage Log Levels to temporarily enable DEBUG logging for workflow and launcher-related classes.
    • Don’t enable DEBUG logging via code deployment for temporary troubleshooting.
    • After collecting logs, revoke DEBUG logging to avoid unnecessary log volume.
    • For more details, refer to Adobe documentation on managing log levels.

  5. Remediate Asset Metadata (if needed)

    • If the affected assets in Production have a different node structure or missing metadata, update the assets so that title changes update the metadata node as expected.
    • This may involve re-saving the asset metadata or using a script to align the node structure with working assets.
recommendation-more-help
experience-cloud-kcs-help-kbarticles