Check AEM as a Cloud Service release versions before go-live
In Adobe Experience Manager as a Cloud Service, Development, Stage, and Production environments can display different AEM release versions during the managed update process. This difference affects code validation, promotion, and go-live readiness when custom code is tested against a different AEM version from the target environment. To fix this, check the release version for each environment in Cloud Manager, use the Production release as the validation baseline, and coordinate with Adobe if an environment remains on an unexpected release.
Description description
Environment
Adobe Experience Manager as a Cloud Service Development, Stage, and Production environments managed through Cloud Manager
Issue/Symptoms
- The Development environment displays a newer AEM release version than Stage or Production.
- Code promotion or validation activities are blocked because the environments use different release versions.
- No specific error message appears, but deployment, review, or go-live activities can’t proceed as planned.
- The version difference becomes important before a major event such as go-live, legal review, or a code freeze.
Cause
AEM as a Cloud Service release updates and custom code deployments are separate events. During the managed release process, Development can temporarily display a different AEM version from Stage and Production. This difference affects validation when custom code is tested against a release that doesn’t match the target environment.
Resolution resolution
To check and address an environment release-version difference, follow these steps:
- Open each Development, Stage, and Production environment in Cloud Manager and record the displayed AEM release version.
- Compare the versions with the Production release used as the baseline for code validation and deployment readiness.
- Review the AEM version-update status and release schedule if Development displays a newer version than Stage or Production.
- If an environment remains on an unexpected or outdated release, contact your Adobe technical representative or Adobe Support.
- Provide the release version displayed for each environment and explain the deployment, go-live, legal-review, or code-freeze impact.
- After the release update completes, check Cloud Manager again and verify the release version for each environment.
- Proceed with deployment, validation, or go-live activities after the release versions and environment health meet your project requirements.
Notes:
- AEM as a Cloud Service release updates are managed separately from custom code deployments. Don’t treat a newer Development release as a request to manually update Stage and Production.