AEM as a Cloud Service: Preventing Stage environment code overwrites during maintenance pipelines
This article explains how the Adobe Experience Manager Cloud Manager production pipeline behaves after performance testing and before deployment to Production. It also clarifies whether manual intervention is required.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
During automatic maintenance or version update pipelines, the system updates the AEM runtime and redeploys the last successfully released Production code to both the Stage and Production environments. If newer code exists only on Stage, such as for user acceptance testing (UAT), the system overwrites it and reverts it to match the last Production release. This behavior is by design and keeps Stage and Production in sync during maintenance updates.
Resolution resolution
Follow these steps to resolve the issue:
-
To recover overwritten user acceptance testing (UAT) work, rerun your Stage + Production pipeline by using the branch that contains your upcoming release.
-
Deploy to Stage, validate your UAT, and approve deployment to Production when ready. You can keep the pipeline blocked at the approval step during UAT to prevent Stage and Production from drifting.
-
To prevent future overwrites during maintenance:
- Avoid leaving unreleased code only on Stage for extended periods. Use Development or Rapid Development Environments (Dev/RDE) for long UAT cycles and keep Stage closely aligned with Production.
- Plan to complete the full Stage + Production pipeline before known maintenance windows so maintenance updates use your new release tag.
- For critical UAT windows where Stage must not be reverted, coordinate with Adobe Support to temporarily pause automatic updates for your program.
-
Monitor upcoming maintenance schedules by using the AEM release updates roadmap and subscribe to AEM notifications in Experience Cloud for update and maintenance information.
-
After you complete these steps, verify that your Stage environment contains the expected code and that your UAT activities can proceed as planned.