Schedule AEM as a Cloud Service maintenance updates around deployments and verify hibernation status
This article explains how to prevent automatic Adobe Experience Manager (AEM) as a Cloud Service maintenance releases from triggering environment hibernation during critical deployment windows, and provides steps to configure scheduling options to avoid deployment validation delays.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- Cloud Manager program with Stage and Production environments
- Automatic maintenance updates enabled for the program
Issue/Symptoms
- Automatic maintenance pipeline triggers during deployment window
- Stage and production environments are marked as hibernated
- Deployment validation is delayed (potentially up to 1.5 hours)
- UI show ‘hibernated’ status even if login is possible
Cause
If Quiet Hours or Update Free Periods aren’t configured, automatic maintenance updates can occur during a critical deployment window and delay validation. These scheduling settings don’t cause or control hibernation. Automatic hibernation applies to environments in Sandbox programs after eight hours of inactivity; Production-program environments can’t be hibernated. If Cloud Manager reports Hibernated while you can access the environment, verify the program type and environment status instead of assuming the status is only a display issue.
Resolution resolution
Follow the steps below to resolve the issue:
-
In Cloud Manager, review the automatic maintenance update activity and the status of the affected environments. Confirm whether the maintenance update has completed.
-
Check the program type and verify the environment status:
- Automatic hibernation applies to environments in Sandbox programs after eight hours of inactivity. If a Sandbox environment is actually hibernated, use the supported De-hibernate action in Cloud Manager or Developer Console, then wait for the environment to become active.
- Production-program environments can’t be hibernated. If Cloud Manager reports Hibernated while you can access the environment, compare the status shown in Cloud Manager and Developer Console.
Note: Don’t assume a Hibernated status is only a display issue. If the status remains inconsistent or blocks pipeline validation, contact Adobe Support.
-
To prevent future automatic maintenance releases from impacting critical deployment windows, configure the following scheduling options:
- Set Quiet Hours to a daily interval of up to eight hours in your local time zone.
- Set an Update Free Period for a seven-day window. You can schedule up to three periods in a floating 365-day window, with at least one week between periods.
-
Follow the current Quiet Hours and Update Free Periods documentation when setting or changing the schedule.
-
After confirming the environments are operational, proceed with release validation and production activities.