AEM Cloud Manager Production deployment fails after prolonged execution with system issue error
This article explains how to troubleshoot and resolve situations where an Adobe Experience Manager (AEM) Cloud Manager Production deployment remains in progress for several hours and ultimately fails with a generic system issue error.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Manager (all versions)
Symptoms
- Production deployment remains in progress for several hours (For example: 6+ hours).
- Cloud Manager reports a generic system issue error upon failure.
- No specific error details are provided in the UI.
- Subsequent deployments are blocked.
Cause
This issue occurs if a Non-Interruptive Maintenance Upgrade (NIMU) is active on the environment, which prevents deployments from proceeding until the upgrade completes. Additionally, large deployment packages containing multiple modules or significant changes under the Sling installer path can cause prolonged bundle restarts and extended deployment times.
Resolution resolution
Follow the steps below to resolve the issue:
-
Check for ongoing NIMU upgrades:
- In Cloud Manager, review the environment’s status for any maintenance or upgrade activities. If a NIMU upgrade is in progress, deployments will wait at the deployment step until the upgrade completes. Note that there may not be a clear UI indicator that a deployment is waiting on NIMU.
-
Review deployment package size and scope:
- Large deployment packages with multiple application modules or extensive changes under the Sling installer path can cause prolonged deployment times. For future deployments, consider reducing the number of modules, third-party packages, and index changes delivered together.
-
Monitor pipeline execution:
- If a NIMU upgrade is ongoing, allow the deployment to proceed. The pipeline should resume automatically once the environment becomes available.
-
Re-execute the deployment:
- Once the environment is healthy, and no NIMU upgrades are in progress, re-run the Production deployment using the same artifact.
-
If the issue persists:
- If deployments continue to fail or remain stuck, collect relevant deployment logs, and contact Adobe Support for further assistance.
Verification: Confirm that the deployment completes successfully and subsequent deployments are unblocked.