Documentation

Missing smart tags on assets after migrating to AEMaaCS

Last update: Thu Feb 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

After migrating assets from Adobe Experience Manager (AEM) 6.5 to Adobe Experience Manager as a Cloud Service (AEMaaCS), smart tags do not appear because post-processing workflows do not run automatically during migration. To resolve the issue, reprocess metadata using the advanced workflow option.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) – Assets

Issue/Symptoms

  • Migrated assets lack smart tags after migration to AEMaaCS.
  • Only a few migrated assets display smart tags correctly.
  • DAM (Digital Asset Management) Smart Tag Assets workflow does not automatically process migrated assets.
  • Bulk-imported or Content Transfer Tool (CTT)-transferred assets remain untagged until reprocessed.

Resolution resolution

Follow these steps to resolve the issue:

  1. Access your AEM as a Cloud Service environment.
  2. Go to Assets and find folders with migrated assets missing smart tags.
  3. Select the folder(s) you want to reprocess.
  4. Start the Asset Update Workflow using the Advanced Reprocess option, and choose Reprocess only metadata.
  5. Confirm that only metadata is selected. This ensures renditions and thumbnails are not affected.
  6. For large volumes, limit each batch to 1,000 assets or fewer to prevent timeouts caused by node hierarchy limits.
  7. Start the workflow. It will recursively process all selected folders and subfolders, generating new AI metadata including smart tags.
  8. After completion, verify that smart tags are added to previously untagged assets.

Notes:

  • Reprocessing only metadata does not affect existing renditions or thumbnails.
  • Technical metadata (file format, image dimensions, document ID, creation/modification dates), extracted binary metadata (EXIF, IPTC, XMP), custom extraction mappings, and schema rules may be updated based on your configuration.
  • If you use custom schemas or extraction mappings, test reprocessing on a single asset in a lower environment before running in production.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f