DocumentationExperience Cloud KCS

AEM: Assets fail to sync with Content Hub and Dynamic Media due to invalid page rendition

Last update: July 31, 2026

This article explains how to resolve asset sync failures to Content Hub and Dynamic Media in Adobe Experience Manager caused by invalid page renditions.

Description description

Environment

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

Issue/Symptoms

Some assets don’t sync to Content Hub and Dynamic Media, even after metadata updates, reprocessing, and approval workflows. The assets remain unsynced despite repeated attempts.

  • Affected assets display no errors in the UI, but don’t appear in Content Hub or Dynamic Media after approval.
  • Manual searching for the assets in Content Hub and Dynamic Media returns no results.
  • No explicit error message is shown to the user, but backend logs may indicate issues with asset approval or delivery requests.

Example asset paths:

  • /content/dam/worldwide-content/gbs/int/en-us/document/produced/2025-feb/users-guide-consulting-marketing-workbench.doc
  • /content/dam/worldwide-content/gbs/int/en-us/document/produced/2025-feb/setup-and-configuration-guide-consulting-marketing-workbench.doc
  • /content/dam/worldwide-content/gbs/int/en-us/document/produced/2025-feb/sales-faq-consulting-marketing-workbench.docx

Cause

The affected assets contained an invalid page rendition node without binary data, causing the approval and downstream sync to Content Hub and Dynamic Media to fail.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Identify Affected Assets

    • Locate assets that aren’t syncing to Content Hub or Dynamic Media, despite successful approval attempts.

  2. Check for Invalid Page Rendition

    • In CRXDE Lite or a similar repository browser, navigate to the asset node.
    • Inspect the /jcr:content/renditions/page node.
    • Confirm if the page rendition exists but lacks the required binary data property (jcr:data).

  3. Remove the Invalid Page Rendition Node

    • Delete the /jcr:content/renditions/page node from each affected asset.

  4. Reprocess the Asset

    • Trigger reprocessing or re-approval for the asset to regenerate renditions and initiate sync to Content Hub and Dynamic Media.

  5. Verify Sync

    • Confirm that the asset now appears in Content Hub and Dynamic Media, as expected.

Preventive Measure

  • Adobe Engineering has implemented a mitigation to exclude the page rendition from asset-delivery approval processing by setting blocked.renditions=[ "page"]. This prevents future approval flows from attempting to read binary data from malformed or non-binary page rendition nodes.
recommendation-more-help
experience-cloud-kcs-help-kbarticles