Conflicts

Obsidian supports completely customizable conflict configuration combined with custom prioritization.

To accommodate your business' needs, any number of jobs can be configured to not run concurrently, even if scheduled to run at the same time. When jobs are set as conflicting and are scheduled to run at the same time, the chosen prioritization will determine the order of execution of the scheduled jobs. Any termination state, either success or failure, will release the next lower priority job to complete. These conflicts work even across multiple hosts.

If you have configured conflicting jobs, you will want to pay attention to the pickup buffer minutes configuration setting and the recovery type - see Job Features.

If you are using recovery type Conflicted, the pickup buffer minutes is not used when determining whether to run a job that had been conflicted. When the higher priority conflict(s) clear, a job with recovery type Conflicted will always run. Pickup buffer minutes is used in other scenarios. This will determine the maximum number of minutes past the original scheduled time that the scheduled job will still be picked once higher priority conflicts have cleared. If this time limit passes, the scheduled job will be marked as Conflict Missed and will not be run.