DocumentationExperience Cloud KCS

AEM as a Cloud Service Dynamic Media: Missing renditions after asset republish

Last update: October 22, 2026

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

This article explains how to address missing Dynamic Media renditions, such as ‘SwatchThumbnail’, for legacy assets after republishing in Adobe Experience Manager as a Cloud Service.

Description description

Environment

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

Symptoms

  • After performing a full republish or reprocess of assets in the production environment, certain Dynamic Media renditions (e.g., SwatchThumbnail) are missing for some assets.
  • The issue primarily affects legacy assets, which may have been migrated from a previous platform or processed with an older profile that did not include the missing rendition.
  • The correct processing profile is applied to the asset path.
  • The expected rendition does not appear in the AEM Assets UI or when accessed directly via Dynamic Media URL.
  • Newly ingested assets or those originally processed with a profile containing the missing rendition are not affected.
  • Removing an existing rendition (e.g., SquareLarge) and reprocessing the asset causes the missing rendition to appear as expected.
  • No specific error messages are present in the UI; the rendition is simply absent.

Cause

Legacy assets processed with older profiles may retain outdated or conflicting renditions, preventing new renditions from being generated during republish. Removing the legacy rendition and reprocessing forces AEM as a Cloud Service to apply the current profile and generate all configured renditions.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Identify assets missing the expected Dynamic Media rendition (e.g., SwatchThumbnail) after republish or reprocess.
  2. Confirm the correct processing profile is applied to these assets.
  3. In AEM Assets, delete the existing rendition (e.g., SquareLarge) from the affected asset.
  4. Trigger a full reprocess of the asset using the current processing profile.
  5. Verify that the missing rendition is now generated and available in both the AEM UI and via Dynamic Media URL.
  6. Repeat these steps for other affected legacy assets as needed.
recommendation-more-help
experience-cloud-kcs-help-kbarticles