Content Hub assets do not sync because approval metadata is misconfigured
Assets do not appear in Content Hub when required approval metadata is missing, disabled, or applied in the wrong place. The issue occurs when dam:status is not editable, dam:activationTarget is missing or mapped incorrectly, or automatic approval is configured in a metadata schema instead of a metadata profile. Assets uploaded directly to Content Hub also remain unavailable when Auto-approval is disabled. To fix this, correct the metadata schema, apply a metadata profile to ingest folders, and enable Content Hub auto-approval when assets are uploaded through Content Hub.
Description description
Environment:
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- AEM Dynamic Media
- AEM Assets Essentials
Issue/Symptoms:
- The Review Status field does not appear or cannot be edited in asset properties.
- Assets uploaded to AEM do not sync to Content Hub even when
dam:statusanddam:activationTargetappear to be set in the schema. - The Add assets option in Content Hub disappears or uploads appear stuck in a loop.
- Assets can be rejected in Content Hub but cannot be reapproved from Admin View.
- Approval options do not appear when using a Classic UI.
Cause:
Content Hub requires explicit approval metadata in AEM Assets. The metadata schema must expose Review Status and allow editing of ./jcr:content/metadata/dam:status. If Approval Target is missing or ./jcr:content/metadata/dam:activationTarget is not configured correctly, synchronization does not occur. Automatic approval for newly ingested assets must be set in a metadata profile, not only in the schema. When assets are uploaded directly in Content Hub, Auto-approval must also be enabled there.
Resolution resolution
To fix this issue, follow these steps:
- Open Cloud Manager and confirm that Content Hub is enabled for the production environment and opens successfully.
- In Admin View, go to Tools
>Assets>Metadata Schemas, open the applicable schema, and verify that Review Status is present on the Basic tab. - In the schema editor, confirm that Review Status maps to
./jcr:content/metadata/dam:statusand that editing is not disabled. - If Review Status is not editable, open the field rules, clear Disable edit, save the schema, and then open an asset to confirm that the Status drop-down is active.
- If Approval Target is missing, add a dropdown field to the schema, map it to
./jcr:content/metadata/dam:activationTarget, and add the valuescontenthubanddelivery. - Go to Tools
>Assets>Metadata Profiles, create a metadata profile and add the required properties so new assets receivedam:status=approvedanddam:activationTarget=contenthub. - Apply the metadata profile to the folders used for ingestion, upload a test asset, and confirm that the approval metadata is applied automatically.
- Compare the schema mapping for
dam:statuswith the metadata profile defaults and remove any conflicting default values that override the profile behavior. - If assets are uploaded through Content Hub, click the person icon, open Configuration
>Import, enable Auto-approval and confirm that uploaded assets appear automatically. - If existing assets still need approval, open Assets View, select the required assets or folder, use Bulk Metadata Edit, and set Status to
Approved. - If approval options do not appear, stop using Classic UI for this task, switch to Assets View, and verify that Review Status and Approval Target are visible.
- Validate the result by uploading a new asset into a folder with the metadata profile applied, confirming that it receives the expected approval metadata, and verifying that it appears in Content Hub without manual intervention.