DocumentationExperience Cloud KCS

Adobe Experience Manager: Updates delayed due to CDN cache

Last update: September 28, 2026

This article describes why updates to pages or redirections in Adobe Experience Manager (AEM) production environments don’t appear immediately, and provides steps to clear CDN cache so the latest content is served.

Description description

In Adobe Experience Manager deployments that use a Content Delivery Network (CDN), updates to published pages or redirections aren’t be visible immediately on the live production site. This is because the CDN continues to serve cached (stale) content, which delays the appearance of recent changes for end users.

Environment

  • Adobe Experience Manager (all versions)
  • Deployments using a CDN in front of AEM

Symptoms

  • Recently published pages or updated redirections don’t appear immediately on the production site.
  • End users see outdated content after changes are published.

Cause

The CDN cache is serving outdated content, preventing the latest updates from being displayed. Clearing the CDN cache forces the CDN to retrieve and serve the most recent content from AEM.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Identify the CDN provider or caching layer used in your AEM production environment (such as Adobe Managed CDN, Amazon CloudFront, Akamai, etc.).

  2. Access the CDN management console or portal provided by your CDN vendor.

  3. Use the cache invalidation or purge feature to clear cached content for the affected URLs or paths. This may involve:

    • Submitting an invalidation request for specific URLs or patterns (For example: updated pages or redirection paths).

    • Using available APIs or tools provided by your CDN vendor to automate cache purging, if needed.

  4. Wait for the invalidation process to complete, as propagation times vary depending on the CDN provider.

  5. Verify that the latest changes are now visible on the production site by refreshing the affected pages.

If you are unsure how to perform cache invalidation for your specific CDN, consult your CDN provider’s documentation or contact your internal web operations team.

recommendation-more-help
experience-cloud-kcs-help-kbarticles