AEM as a Cloud Service: Purging CDN cache in the DEV environment
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article explains how to resolve the issue where updates made in the AEM as a Cloud Service DEV environment are not visible due to CDN caching, by performing a self-service CDN cache purge.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions)
Symptoms
- Updates made in the DEV environment (such as changes to
robots.txt) are not visible when accessing the site via its public URL. - Search engines may receive outdated content, which can lead to unintended crawling of the site.
- There are no explicit error messages, but there is a mismatch between expected and actual site content after updates.
Cause
The CDN cache was not purged after content updates, resulting in outdated content being served from cache. A manual cache purge is required to reflect changes immediately.
Resolution resolution
Follow the steps below to resolve the issue:
- Verify that you have self-service CDN purge-key configuration and cache purging capability through Cloud Manager.
- Configure the CDN purge token in Cloud Manager, ensuring it is set for the correct environment (DEV).
- Use Cloud Manager to initiate a CDN cache purge for the DEV environment. Refer to the official Adobe documentation for detailed instructions.
- After purging, verify that the updated content (such as
robots.txt) is visible at the public URL. - Confirm that search engines and users receive the latest version of the site content.
- If you encounter errors or are unable to complete the setup, collect the configuration pipeline execution URL and purge request/response (with any secret values redacted) and contact Adobe Support for further assistance.
recommendation-more-help
experience-cloud-kcs-help-kbarticles