AEM as a Cloud Service environments show as hibernated in Developer Console

This article explains how to address situations where Adobe Experience Manager as a Cloud Service (AEMaaCS) environments appear as Hibernated in the Developer Console even though the environments remain active and accessible. This issue affects the Developer Console user interface and can limit access to expected environment information, while the actual Author and Publish services continue to operate normally. To resolve the issue, verify environment availability and use the classic Developer Console until the status is corrected.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • AEM as a Cloud Service environments appear with a Hibernated status in the Developer Console even though they remain operational.
  • Environment information may not be available through the Developer Console.
  • Author and Publish environments remain accessible through their direct URLs.
  • The issue occurs in the newer Developer Console interface and does not affect actual environment availability.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Access the AEM as a Cloud Service Author or Publish environment directly by using the appropriate URLs and confirm that the environment is operational.
  2. Use the classic Developer Console to review environment status and access environment details such as OSGi bundle information and Local Development Access Tokens.
  3. If the new Developer Console displays the environment as Hibernated but direct access confirms that the environment is active, treat the behavior as a Developer Console status-reporting issue.
  4. Continue using the classic Developer Console for environment management and diagnostics until the environment status displays correctly in the newer Developer Console.
  5. If the Hibernated status persists or occurs again, capture a screenshot of the Developer Console and record the approximate time of the occurrence.
  6. Contact Adobe Support and provide the screenshot together with the recorded time details to assist with further investigation.
  7. Verify the resolution by confirming that the Developer Console displays the correct environment status and that all expected environment information is available.
recommendation-more-help
experience-cloud-kcs-help-kbarticles