Dynamic Media assets published with preview domain metadata cause 403 errors in AEM as a Cloud Service

Last update: September 10, 2026

This article describes how to resolve an issue in Adobe Experience Manager (AEM) as a Cloud Service where Dynamic Media assets are published with preview domain metadata, resulting in image load failures and HTTP 403 errors on production sites.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms

In some scenarios, Dynamic Media assets published from AEM as a Cloud Service may contain incorrect metadata, causing image URLs on production pages to reference the preview domain instead of the production Scene7 domain. This leads to HTTP 403 errors and images failing to render on live sites.

Some images on production pages fail to load.
Image URLs reference the Dynamic Media preview domain (for example, https://preview1.assetsadobe.com/is/image/...) instead of the production Scene7 domain (for example, https://s7d1.scene7.com/is/image/...).
Affected assets have metadata fields such as dam:scene7Domain set to the preview domain and dam:scene7FileStatus set to PublishIncomplete.

Cause

This issue is typically caused by a misconfiguration or replication problem in Dynamic Media settings, resulting in incorrect metadata assignment during asset publication. The preview domain is intended for author environments only and is not accessible from production, leading to HTTP 403 errors.

Resolution resolution

Follow the steps below to resolve the issue:

Identify affected assets.
- Use browser Developer Tools to inspect image URLs on production pages.
- Look for URLs referencing the preview domain (for example, preview1.assetsadobe.com).
Check asset metadata in AEM.
- For affected assets, review the metadata fields dam:scene7Domain and dam:scene7FileStatus.
- Confirm that they are set to the preview domain and PublishIncomplete.
Correct Dynamic Media configuration.
- In the AEM author environment, review and re-save the Dynamic Media configuration to ensure the correct Scene7 production domain is set.
Reprocess affected assets.
- Unpublish the affected asset.
- Reprocess the asset in AEM to update its metadata.
- Republish the asset to Dynamic Media.
Republish affected pages.
- Republish any pages containing the affected assets to ensure updated URLs are reflected on live sites.
Verify resolution.
- Confirm that image URLs now reference the production Scene7 domain and that images render correctly on production pages.
Monitor for recurrence.
- Continue to monitor production pages for similar symptoms.
- If the issue recurs, collect examples of affected and unaffected asset URLs, screenshots of metadata fields, and HTTP response codes for further analysis.