Documentation

Edge Delivery Services Sites not rendering correct AEM Stage/Production content

Last update: Tue May 13 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When using Edge Delivery Services (EDS) in repoless configurations in the Adobe Experience Manager (AEM) as a Cloud Service, the rendered content is not as expected in the stage and production environments. To fix this issue, verify technical account configuration, check EDS configuration, update cloud configurations, and review error logs.

Description description

Environment

Adobe Experience Manager (AEM) as a Cloud Service - Sites

Issue/Symptoms

  • Stage and Production EDS sites don’t display the expected content from AEM.
  • URLs for published pages show a 404 error, despite successful publishing in AEM.
  • Assets and pages appear inconsistently or aren’t delivered to EDS.
  • Configuration differences between environments were identified.

Resolution resolution

To resolve the issue of incorrect rendering of AEM content on Stage and Production EDS sites, follow these steps:

  1. Ensure that the technical account user is correctly configured for each environment and has the required permissions to access DAM resources. For example, Stage should use a dedicated technical account, separate from Development or Production.
  2. Navigate to Tools > Cloud Services > Edge Delivery Services Configuration in AEM Author. Confirm the site name and configuration match the target environment (for example, client-digital-experience-stage for Stage).
  3. Check that cloud configuration settings are correctly applied. Make sure asset properties under Cloud Services  point to the correct paths (for example, /conf/clientdigitalexperience-stage for Stage).
  4. Publish all required pages, assets, and GraphQL endpoints from AEM Author to ensure they are available in EDS.
    • Note: Initial publishing may experience delays due to system throttling during high-volume requests.
  5. Use the following Splunk query to check publish logs for warnings or errors: index="dx_aem_engineering" sourcetype=aemerror aem_service=cm-p1xxx14-e1xxx672 aem_tier=publish (level=ERROR OR level=WARN)
    • Review logs for issues related to asset delivery or caching.
  6. If outdated content is being served, clear caching layers such as AEM Dispatcher, Adobe CDN (Fastly), or any custom CDN/WAF. Each layer may need to be cleared during troubleshooting or deployments.
  7. Use the AEM Purge CDN Cache API for self-service cache invalidation. Don’t rely solely on TTLs if immediate content freshness is needed.
  8. Use incognito mode or clear your browser cache to test if published updates appear correctly. Also, compare configurations across Development, Stage, and Production to spot any discrepancies.
  9. After completing these steps, verify that URLs previously returning 404 errors now load the correct content.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f