DocumentationExperience Cloud KCS

Delayed content updates in Adobe Experience Manager due to Dispatcher statfileslevel configuration

Last update: October 6, 2026

This article explains how to address delays in content updates appearing on the publish environment after replication from the author environment in Adobe Experience Manager (AEM), focusing on the Dispatcher cache statfileslevel configuration.

Description description

Environment

  • Adobe Experience Manager (AEM)
  • Dispatcher cache

Issue/Symptoms

  • When content is published from the AEM author environment, it should appear promptly on the publish environment.
  • Updates to pages or assets may take several hours to appear, even though the replication queue processes items quickly and no errors are reported.
  • This issue can affect all types of content.
  • The issue occurs regardless of whether the CDN cache is disabled or the Dispatcher cache is manually cleared.

Cause

The Dispatcher cache is not being invalidated as expected because of the statfileslevel configuration. If the statfileslevel value is lower than the depth of the site’s content paths, cache invalidation does not occur for deeper paths, causing stale content to remain until cache expiration.

Resolution resolution

To fix delayed content updates caused by Dispatcher statfileslevel configuration, follow these steps:

  1. Review your current Dispatcher configuration file (typically dispatcher.any or dispatcher.yaml).
  2. Locate the statfileslevel parameter in the /cache section of the configuration.
  3. Determine the maximum depth of your content paths (for example, /content/site/section/page is depth 4).
  4. If your content is nested deeper than the current statfileslevel value, increase statfileslevel to match or exceed the maximum depth of your content paths.
  5. Save the configuration file, and reload or restart Dispatcher to apply the changes.
  6. Clear the Dispatcher cache to remove any outdated content.
  7. Republish a page or asset and verify that the update appears promptly on the publish environment.
  8. Coordinate with your team to ensure the new statfileslevel value aligns with your caching strategy and does not cause unnecessary cache invalidation.
recommendation-more-help
experience-cloud-kcs-help-kbarticles