AEM as a Cloud Service: Automatic page version purge configuration
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article explains the configuration options and best practices for enabling automatic page version purging in Adobe Experience Manager as a Cloud Service, including current recommendations and future considerations.
Description description
Environment
- Adobe Experience Manager as a Cloud Service (all versions)
Symptoms
Questions arise regarding the configuration and enablement of automatic page version purging, including:
- Reasons for Adobe’s caution in enabling this feature
- When default enablement may be introduced in future AEM SDK versions
- Appropriate configuration values for maximum versions retained, maximum version age, and minimum versions retained
No error messages or stack traces are present. The issue concerns configuration best practices and future product roadmap.
Cause
Automatic page version purging is not enabled by default to prevent accidental data loss and to allow organizations to control their version retention policies.
Resolution resolution
Follow the steps below to configure automatic page version purging:
-
Review the official Adobe documentation on Maintenance Tasks in AEM as a Cloud Service for the latest guidance on automatic page version purging.
-
Understand that Adobe advises caution when enabling this feature to prevent unintended loss of important page versions, especially in environments where version history is important for compliance or rollback.
-
Note that there is currently no confirmed AEM SDK version or release date for default enablement of automatic page version purging. Any changes to default behavior will be communicated in the AEM release notes.
-
For current AEM as a Cloud Service programs, manage configuration manually via the Cloud Manager configuration pipeline.
-
The following configuration values are valid:
-
Maximum versions retained: 5
-
Maximum version age: 30 days
-
Minimum versions retained: 5
-
-
Deploy configuration changes through the Cloud Manager configuration pipeline following standard procedures.
Verify that at least five versions are always retained, even if they exceed the maximum age.