DocumentationExperience Cloud KCS

DAM assets not syncing to Dynamic Media or generating Smart Crops

Last update: October 6, 2026

This article provides troubleshooting steps for situations where assets uploaded to Adobe Experience Manager (AEM) Digital Asset Management (DAM) do not sync to Dynamic Media or fail to generate Smart Crops. It covers common causes and actionable solutions to restore expected asset processing.

Description description

Environment

  • Adobe Experience Manager (AEM) Managed Services
  • Dynamic Media integration enabled

Issue/Symptoms

  • Assets uploaded to DAM do not sync to Dynamic Media (Scene7)
  • Smart Crops are not generated for affected assets
  • Affected assets may not have Scene7-related properties in their asset metadata
  • The issue is reproducible with multiple assets

Cause

  • Required workflows for Dynamic Media sync or Smart Crop generation are disabled or blocked
  • Metadata write conflicts (such as OakState0001) during asset moves or concurrent processing
  • Temporary platform-side outages in the Smart Crop service
  • Invalid Smart Crop profile configuration (e.g., unsupported aspect ratios)

Resolution resolution

To fix assets that do not sync to Dynamic Media or generate Smart Crops, follow these steps:

  1. Check whether the affected asset appears in Dynamic Media (Scene7) and review its metadata (JSON) in AEM for Scene7-related properties, such as dam:s7damType or dam:imageServerAsset.
  2. Ensure that all required workflows for Dynamic Media sync and Smart Crop generation are enabled.
  3. Check for custom launcher workflows that may block or interfere with the standard Dynamic Media workflows.
  4. Confirm that the folder containing the affected assets has the correct Image Profile or Smart Crop Profile.
  5. Open the Smart Crop or Image Profile assigned to the affected folder and verify that all Smart Crop dimensions use supported aspect ratios (between 0.05 and 20).
  6. Adjust or remove any invalid aspect ratios, then reprocess the affected assets.
  7. Review AEM error logs for OakState0001 or similar metadata write conflict errors during asset moves into Dynamic Media folders.
  8. Avoid running custom reprocessing workflows and Scene7 sync workflows simultaneously on the same asset.
  9. If the issue occurred during a known outage window (for example, when the Smart Crop service was unavailable), re-upload or reprocess the affected assets after service restoration to trigger Smart Crop generation.
  10. If assets still fail to sync or Smart Crops are not generated and you find no workflow or outage issues, contact Adobe Support and provide asset paths, upload timestamps, and relevant error logs.

After performing the above steps, confirm that assets appear in Dynamic Media and that Smart Crops are generated as expected.

recommendation-more-help
experience-cloud-kcs-help-kbarticles