Conflicts: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
Created page with "Espresso supports completely customizable conflict configuration with built-in prioritization." |
No edit summary |
||
| Line 1: | Line 1: | ||
Espresso supports completely customizable conflict configuration with | Espresso 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 conflicting jobs that | |||
Revision as of 03:06, 21 February 2011
Espresso 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 conflicting jobs that
