Delay for a conflicting job
The batch process does not start a renewal job if there is a conflicting job. A conflicting job is an open policy change or cancellation job. A policy that would normally renew on a given day will wait three additional days to start if there is a conflicting job. After three days, the next run of the batch process starts the renewal, whether or not there is an open conflicting job.
The three day delay is set in the CONCURRENT_JOB_DELAY_DAYS variable
which is defined in the Renewal plugin. You can modify how this plugin
calculates and uses the delay for a conflicting job.
Note: The frequency of the batch process
is a factor in when a delayed renewal starts. For example, you have a
batch process that runs every Sunday. A delayed renewal that could start
on Wednesday will not start until the batch process runs on Sunday, several
days later.