DocumentationExperience Cloud KCS

Updated assets aren’t immediately visible at Dynamic Media with OpenAPI delivery URLs in AEM as a Cloud Service

Last update: October 15, 2026

This article outlines the expected timing for asset publication to Dynamic Media in Adobe Experience Manager as a Cloud Service, explains current limitations with status indicators, and provides steps to verify asset availability and manage cache if updates are delayed.

Description description

Environment

  • Adobe Experience Manager Assets as a Cloud Service
  • Dynamic Media with OpenAPI enabled

Issue/Symptoms

  • After an approved asset is updated, the new content remains unavailable at its Dynamic Media with OpenAPI delivery URL for more than 15 minutes.
  • There is no visible status indicator in the Admin UI or Assets View to confirm when an asset has been successfully pushed to Dynamic Media.

Cause

The observed delay is typically due to the configured CDN cache Time-to-Live (TTL) for Dynamic Media, which is set to 10 minutes. The absence of a status indicator is a current product limitation in the UI.

Resolution resolution

Follow the steps below to address the issue:

  1. In Assets View, select the affected asset and confirm that its status is Approved and its approval target is Delivery. Dynamic Media with OpenAPI delivers approved assets with the Delivery target.
  2. After an approved asset is updated, allow up to 10 minutes for the change to appear at its Dynamic Media with OpenAPI delivery URL. Adobe documents that approved asset updates become visible in delivery URLs in under 10 minutes.
  3. Open the asset’s Dynamic Media with OpenAPI delivery URL and verify that it returns the updated content.
  4. If the delivery URL still returns the previous content after 10 minutes, check whether a browser or customer-managed CDN is serving a cached response. If needed, use the documented AEM CDN cache-invalidation process to purge the specific delivery URL. Note: Manual CDN purging requires a configured Purge API Token. Purge the specific resource rather than the full cache; hard or full purges increase traffic to the origin. See Purging the CDN cache and Cache Management in Dynamic Media with Open APIs.
  5. If the updated content remains unavailable after the documented propagation window and cache checks, collect the update time, asset ID, delivery URL, and steps to reproduce. Share these details through an Adobe Support case.
recommendation-more-help
experience-cloud-kcs-help-kbarticles