Due to CMS-9267, the PurgeContentsScheduler should be deactivated to avoid issues in the client repositories. It is based on the data currentStepId but it shouldn't because this data is not up to date in the version history.
- Référence
-
CMS-9267 The currentStepId in the history is not consistent
- Open