Published content not updating on CDN domains in Adobe Experience Manager as a Cloud Service
In Adobe Experience Manager as a Cloud Service, published content changes may not appear when users access pages through CDN domains, even though the updates are available on publish instances. This behavior is often related to caching layers or Link Checker configuration on the publish environment. To fix this issue, review cache invalidation across CDN layers and verify the Link Checker configuration.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions)
Symptoms
- Published content changes are not visible on CDN domain URLs (for example, https://).
- No error messages are shown to end users.
- The author environment displays updates correctly.
Cause
The Link Checker on the publish instance may disable or modify links, resulting in updated content not being reflected on CDN domains. Caching layers may also serve outdated content if cache invalidation is not performed.
Resolution resolution
Follow these steps to resolve the issue:
- Access the publish instance directly (not through the CDN domain) to confirm that the updated content is present and visible.
- Review the CDN and Dispatcher caching layers to verify that cache invalidation is functioning as expected.
- If necessary, perform a manual cache flush on both the Dispatcher and CDN layers to clear stale content.
- On the publish instance, review the Link Checker settings.
- Determine whether the Link Checker is disabling or modifying links on publish pages, which prevents updated content from being displayed through the CDN.
- Adjust the Link Checker configuration to ensure valid links are not disabled on publish pages.
- After making these changes, monitor the CDN domain to confirm that published changes are visible.
- Validate multiple affected URLs to confirm consistent behavior.
recommendation-more-help
experience-cloud-kcs-help-kbarticles