How to restrict the purge and archive agent schedule only runs on one node at a time?
In our production environment, Pega OOTB Purge&Archive is running on 2 BackGroundNodes. That should not happen. Both are selecting the same cases for purging. So when the case is purged on one node the other node will give an error.
I would like to know steps and configuration details on how to restrict the purge and archive agent schedule to runs only on one node at a time? Which agent, agent schedules needs to be modified to achieve this configuration.
In recent Pega versions (7.1+) the archive/purge (A/P) process, when scheduled, is executed by the ServiceLevelEvents agent.
This is a multi-node agent ensuring that the same event is processed by a single node at time.
The reported issue could be caused by overlapping A/P job executions. In such case please verify the A/P job scheduling and ensure that the amount of items to be processed for the job can be completed before the next run.