Documentation

Inconsistent Version Purging in AEMaaCS

Last update: Tue Mar 17 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

In AEMaaCS, inconsistent version purging occurs when multiple configuration mechanisms are active at the same time. This leads to delayed or unpredictable purging, retention of more versions than expected, and unpurged DAM asset versions. To fix this, use the MaintenanceTasks YAML as the sole configuration for bulk version purging and remove any legacy configurations.

Description description

Environment

Adobe Experience Manager (AEM) as a Cloud Service

Issue/Symptoms

  • Version purging does not trigger or follows incorrect rules when using YAML-based maintenance configuration.
  • Legacy granite_daily and VersionManagerImpl configurations cause delayed or inconsistent execution.
  • More versions are retained than configured (for example, 3 instead of 1).
  • DAM asset versions remain unpurged.
  • Logs do not clearly indicate execution timing or scope.

Resolution resolution

To fix this issue, follow these steps:

  1. Deploy the MaintenanceTasks YAML configuration via the Config pipeline to define version purge rules, including paths, maximum age, and minimum or maximum versions.
  2. Remove all legacy Granite and VersionPurgeTask OSGi configurations from the environment to prevent overlapping logic.
  3. Use VersionManagerImpl only if per-save pruning is explicitly required; otherwise, disable it.
  4. Allow the Adobe-managed weekly maintenance window to execute the purge job according to your deployed YAML rules. The schedule is fixed per environment and is not affected by deployment time.
  5. After the next scheduled maintenance window, review logs and check version counts to confirm that purging occurs as expected.

Notes:

  • The bulk version purge job runs on a fixed weekly schedule managed by Adobe. Customers cannot change this schedule but can control purge rules via YAML.
  • Only one mechanism should be active for predictable results, preferably the YAML-driven job supported by AEM as a Cloud Service.
  • The minNumberVersions setting specifies a minimum number of versions to retain, not an exact count.
  • Purge behavior becomes consistent once only the YAML-driven job is used.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f