AEM as a Cloud Service Author DEV environment stuck in hibernated state
This article provides steps to troubleshoot and resolve situations where an Adobe Experience Manager (AEM) as a Cloud Service Author DEV environment remains in the hibernated state and cannot be de-hibernated using Cloud Manager.
Description description
Environment
- Adobe Experience Manager (AEM) as a Cloud Service
- Author DEV environment
Issue/Symptoms
- The Author DEV environment remains in the Hibernated state after attempts to de-hibernate using Cloud Manager.
- The environment does not transition to a running state.
- Errors such as Failed to load page or HTTP 500 errors may be displayed.
Cause
This issue can occur due to pending deployments, platform-level defects, or internal configuration issues that prevent the environment from starting successfully.
Resolution resolution
To fix the issue where an AEMaaCS Author DEV environment cannot be de-hibernated, follow these steps:
-
Log in to Cloud Manager and navigate to the affected Author DEV environment.
-
Confirm that the environment status is Hibernated.
-
Attempt to de-hibernate the environment by clicking the De-hibernate button in Cloud Manager.
-
Wait several minutes for the environment to transition to the Starting or Running state.
-
If the environment remains in Hibernated or Starting for more than 30 minutes:
a. Check for any pending deployments or pipeline executions in Cloud Manager. If any are in progress or failed, resolve them before attempting to de-hibernate again.
b. Ensure there are no scheduled changes or deployments that could block the de-hibernation process.
-
If the environment still does not de-hibernate after these steps, or if you encounter repeated errors (such as HTTP 500 errors or the environment never reaches Running), collect relevant error messages and contact Adobe Support for further assistance. Provide details about the issue, steps taken, and any error messages observed.