AEM as a Cloud Service: Dynamic Media assets not reprocessed after Content Copy

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article explains why Dynamic Media assets are not automatically reprocessed after performing a Content Copy between AEM as a Cloud Service environments and provides guidance on how to resolve the issue.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Symptoms

  • After performing a DAM/Content Copy from one environment to another, Dynamic Media assets appear in the target environment’s DAM.
  • These assets are not processed according to the Dynamic Media configuration of the target environment.
  • Affected images are not rendered in AEM Author or on the frontend, and Smart Crops are not generated as expected.
  • The property dam:scene7FileStatus = PublishComplete is present on the assets, indicating a completed Dynamic Media publishing state.
  • There is no evidence of Dynamic Media reprocessing or reupload workflows being triggered for these assets after the content copy.
  • Manual reprocessing of the assets resolves the issue.
  • No specific error messages are logged, but expected workflow executions and image processing outcomes are missing.

Cause

The Content Copy process preserves Dynamic Media metadata, including publish status, but does not trigger reprocessing or reupload workflows in the target environment. This results in assets not being processed according to the target environment’s Dynamic Media configuration until manually reprocessed.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Manually trigger the Dynamic Media reprocessing or reupload workflow for affected assets in the target environment.
  2. Confirm that Smart Crops and other Dynamic Media features are generated as expected after manual reprocessing.

This behavior is expected and is a known limitation of the Content Copy feature in AEM as a Cloud Service when used with Dynamic Media assets. There is no automatic mechanism to reprocess Dynamic Media assets post-copy; manual intervention is required.

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