Dispatcher cache is cleared and warmed up after deployment in AEMaaCS
In AEMaaCS, the dispatcher cache is cleared after deploying code to production using the Cloud Manager pipeline. The system then warms up the cache automatically, but details about which pages are selected and how the process works are often unclear. This article explains how cache warmup works after deployments and which pages are prioritized.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- After deployment, the dispatcher cache is cleared.
- The system automatically starts a cache warmup process after flushing, but details about which pages are warmed up and how they’re chosen are unclear.
Resolution resolution
The following steps explain the dispatcher cache warm-up process -
-
Deploy code to the production environment using the Cloud Manager pipeline.
-
Allow the system to complete the full-stack deployment process, which creates new publish instances.
Note: After the dispatcher cache is completely cleared by the system, the cloud infrastructure automatically triggers the cache warmup procedure (this step is not directly configurable).
-
The warmup typically targets high-priority pages such as the homepage, main navigation pages, and other frequently accessed content.
-
Page selection for warmup is determined by internal configuration settings based on traffic analysis and default priorities.
-
Verify that key site pages load quickly after deployment, confirming successful cache warming.
Note: The cache warmup strategy is managed internally by Adobe’s cloud infrastructure and cannot be customized or configured directly by administrators. Adobe doesn’t provide documentation about page selection criteria beyond the general prioritization of frequently accessed content.