Over time, document versions can accumulate significantly. For example, each publish action creates a new version. Without intervention, this can eventually lead to millions of unnecessary versions. To address this, the Version Store schedules a cleanup job, triggered by a cron expression, to remove excess versions. This process is referred to as version decluttering. For details on available settings, see Configuring the Sophora Server.
A version is considered obsolete if one of the following conditions is met:
- The number of versions per document is exceeded.
- The maximum age of a version is exceeded.
Please note that there will always remain at least 15 versions of a document even if these are older than the configured maximum age. However this is independent from the configured maximum number of versions (there may be less than 15 versions if the maximum number of versions is below 15). The lower bound is not configurable.
You can configure both conditions on a global level and on a node type level. On a document level you also have the ability to overwrite the maximum number of versions using the property sophora:maxVersionsToKeep. By default no such limit is set.