DocumentationExperience Cloud KCS

Smart Tags not generated due to folder-level disablement or workflow misconfiguration

Last update: June 27, 2026

Smart Tags fail to generate in AEM Assets when the upload source folder has Smart Tags disabled or when the DAM Update Asset workflow is out of sync, even though the metadata schema is correct and the IMS configuration is healthy. In AEM as a Cloud Service, this often affects assets moved programmatically from a folder where Smart Tags were disabled. In AEM 6.5 Managed Services, a desynchronized DAM Update Asset workflow model prevents the Smart Tags step from running, and no explicit log errors appear. To fix the issue, enable Smart Tags on all source and destination folders or sync the DAM Update Asset workflow model, depending on which path applies.

Description description

Environment:

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • Adobe Experience Manager 6.5

Issue/Symptoms:

  • The Smart Tags field is missing in the asset Properties > Basic tab.
  • Newly uploaded assets do not receive Smart Tags even though the IMS configuration health check passes.
  • Smart Tags work in some folders but not in others.
  • Smart Tags generate correctly with the Smart Tag workflow but not with the DAM Update Asset workflow.

Root cause:

Smart Tag generation depends on both folder-level Smart Tag enablement and correct execution of the DAM Update Asset workflow. In AEM as a Cloud Service, Smart Tags were disabled on the original upload folder, so assets moved programmatically inherited the missing smart-tagging step. In AEM 6.5 Managed Services, the DAM Update Asset workflow model was out of sync, which prevented the Smart Tags workflow step from running.

How to confirm

  1. Check whether Smart Tags fail only in a specific folder or fail globally. If tags fail only for certain folders, use the folder configuration path. If tags fail in all folders, use the workflow path.
  2. If uncertain, upload the same asset to two different folders and compare the results.

Resolution resolution

Resolution (folder configuration path - AEM as a Cloud Service)

  1. Go to the affected folder and open Properties > Cloud Services / Smart Tags. Confirm Smart Tags are enabled not only on the final destination folder but also on any upload or staging folder used for programmatic movement. If disabled, enable Smart Tags.
  2. Select Save & Close in folder properties, then reopen the properties to confirm Smart Tags remain enabled.
  3. Upload a new image directly into the source folder. Smart Tags should appear in the asset’s Properties > Basic tab after processing. Ensure the asset was uploaded directly to the folder, not moved programmatically.

Resolution (workflow path - AEM 6.5 Managed Services)

  1. Go to Tools > Security > Adobe IMS Configurations and confirm the IMS configuration for Smart Tags exists and passes its health check. The validateConfigs() JMX test should report PASS. If it fails, reconfigure IMS before proceeding.
  2. Go to Tools > Workflow > Models > DAM Update Asset and confirm the Smart Tags workflow step exists and is enabled.
  3. Open the DAM Update Asset workflow model and select Sync. Reopen the model and confirm no errors or outdated notes appear.
  4. Upload a new image to any DAM folder with Smart Tags enabled and confirm Smart Tags appear under Properties > Basic. If they do not appear, clear the browser cache and retry.
  5. Validate cross-folder behavior by uploading the same asset to a known-working folder and a previously failing folder, and confirm both now populate Smart Tags.
recommendation-more-help
experience-cloud-kcs-help-kbarticles