DocumentationExperience Cloud KCS

Published page updates or redirects aren’t immediately visible in AEM due to CDN caching

Last update: October 29, 2026

When a published page or redirect update is not visible on the production site, first confirm that the change is published or deployed to the layer that serves it. Then identify whether the stale response is at Dispatcher, Adobe’s CDN, or a customer-managed CDN. To restore the updated response, purge the affected cache layer using its supported method and verify the result.

Description description

Environment

  • Adobe Experience Manager
  • Customer-managed CDN, such as AWS CloudFront or Akamai

Issue/Symptoms

  • Recently published page changes or updated redirects aren’t visible on the Production site.
  • Users receive outdated content or encounter incorrect redirects.

Cause

The customer-managed CDN continues to serve cached content after you publish updates in AEM. As a result, users receive outdated pages or redirects until the cached entries expire or are invalidated. Invalidating the CDN cache forces the CDN to retrieve the latest content from the origin server.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Identify the CDN provider used for the AEM production environment, such as AWS CloudFront or Akamai.
  2. Verify that you have permission to manage CDN cache invalidation. This process typically requires administrative access to the CDN provider’s management console or API.
  3. Sign in to the CDN provider’s management console.
  4. Locate the cache invalidation or purge feature. For example, in AWS CloudFront, open the Invalidations section for the affected distribution.
  5. Create an invalidation request for the paths that require refreshing, such as the specific pages or redirect paths that you updated.
  6. If several files require invalidation and your CDN provider supports wildcard invalidations, use an appropriate wildcard path.
  7. Submit the invalidation request and allow the CDN provider to complete the process. Completion time depends on the CDN provider and the number of paths included in the request.
  8. After the invalidation is complete, verify that the updated pages or redirects appear correctly on the production site.
recommendation-more-help
experience-cloud-kcs-help-kbarticles