Cloud Manager deployment timeout during environment ownership by NIMU or Release Orchestrator
This article explains how Cloud Manager deployment timeouts can occur when the deployment timer includes periods where the environment is held by NIMU or Release Orchestrator processes, and provides guidance on how to avoid and address this scenario.
Description description
During Adobe Experience Manager Cloud Manager deployments, the deployment process enters a waiting state if the environment is currently owned by a NIMU upgrade or Release Orchestrator process. The time spent waiting for the environment to become available is included in the overall deployment step’s completion window (typically around 6 hours). If the combined waiting and deployment time exceeds this window, the deployment may time out, even if the deployment itself is progressing as expected.
Environment
- Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
- Cloud Manager deployments
Symptoms
- Deployment logs show an extended duration at steps such as
wait-for-env-ready. - No specific error message is generated during the wait period.
- Deployment may time out if the total time (waiting plus deployment) exceeds the allowed window.
Cause
The Cloud Manager deployment timer doesn’t pause during periods when the environment is held by NIMU or Release Orchestrator processes. This reduces the effective time available for the deployment itself and can result in timeouts.
Resolution resolution
Follow the steps below to resolve the issue:
-
Before scheduling a Cloud Manager deployment, check for any planned NIMU upgrades or Release Orchestrator activities that may overlap with your deployment window.
-
Schedule deployments to avoid known maintenance windows or upgrade periods, where possible.
-
Monitor deployment logs for extended wait periods at steps such as
wait-for-env-ready. -
If a deployment times out due to environment ownership conflicts:
-
Collect relevant deployment logs showing the extended wait period and timeout.
-
Raise a support case with Adobe, providing the deployment logs and a description of the timing issue.
-
-
Track updates on enhancements to deployment timer behavior through Adobe’s public release notes or support channels.
To verify resolution, confirm that deployments complete successfully without timing out when not overlapping with NIMU or Release Orchestrator activities.