AEM Cloud Manager deployment delayed at ‘Updating indexes’ with no index changes
This article explains how to investigate extended deployment durations in Adobe Experience Manager (AEM) Cloud Manager when a pipeline remains at the Updating Indexes step even though no index changes are included in the deployment. Additional time may be required for environment rollout readiness and reconciliation of AEM services and author pods, which can occur as part of the standard deployment process. To resolve the issue, review deployment logs and validate the environment rollout.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Manager, all versions
Issue/Symptoms
- Stage or production deployments take significantly longer than expected, for example, 1 hour 15 minutes instead of 20 to 40 minutes.
- The pipeline remains at the Updating Indexes step for an extended period.
- No index changes are included in the deployment code.
- The deployment completes successfully without errors or timeouts in the logs.
Root cause
The extended deployment duration is typically related to additional time required for environment rollout readiness and reconciliation of AEM services and author pods. This process can delay the deployment even when no index changes are involved. The Updating Indexes status may appear during this period as part of the standard deployment workflow.
Resolution resolution
Follow the steps below to resolve the issue:
- Review the Cloud Manager pipeline execution details for the affected deployment and access the pipeline execution logs through the Cloud Manager interface.
- In the logs, look for entries that indicate extended time spent on environment rollout readiness or reconciliation of AEM services and author pods. Review any health-check execution delays or shutdown-related messages during this period.
- Confirm that no index-update failures or deployment timeouts appear in the logs. If such errors exist, investigate them separately.
- If the deployment completes successfully and no errors are present, recognize that the delay was likely caused by environment rollout and service reconciliation activities. No further action is required unless the issue recurs.
- If similar delays occur in future deployments and affect release schedules, contact Adobe Support for further investigation.
- Verify the resolution by confirming that the deployment completes successfully and that no errors or timeouts appear in the logs.