AEM as a Cloud Service: Environment status inconsistency between Cloud Manager and Developer Console
This article explains how to resolve situations where the environment status in AEM as a Cloud Service appears inconsistent between Cloud Manager and the Developer Console (Beta), including cases where the Developer Console shows the environment as stuck in the Starting state.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
Issue/Symptoms
- The Cloud Manager environment view displays the environment as Available.
- The Developer Console (Beta) shows the same environment as hibernated or stuck in the Starting state after a de-hibernate action.
- The Starting status message persists for an extended period with no progress.
- There is no impact on environment availability or functionality. The issue is limited to the Developer Console (Beta) display.
Cause
This issue is caused by a display bug in the AEM Developer Console (Beta), which can show an incorrect environment status, such as hibernated or Starting, even when the environment is available and running. Cloud Manager reflects the actual environment status.
Resolution resolution
Follow these steps to resolve the issue:
- Access your environment through Cloud Manager to confirm its actual operational status.
- Do not rely solely on the Developer Console (Beta) for environment status because it can display outdated or incorrect information.
- If you need to verify the environment status, select Back to classic console in the Developer Console to view accurate information.
- If Cloud Manager shows the environment as Available, the environment is operational and no restart or further action is required.
- Monitor Adobe release notes or communications for updates about a fix for this display issue.
recommendation-more-help
experience-cloud-kcs-help-kbarticles