Admin Job Conflicts

From Obsidian Scheduler
Revision as of 22:26, 29 June 2016 by Carfey (talk | contribs) (Created page with "Job conflicts can be configured to prevent jobs in the same set from running at the same time. This screen can be accessed by all users from the primary navigation sidebar, un...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Job conflicts can be configured to prevent jobs in the same set from running at the same time. This screen can be accessed by all users from the primary navigation sidebar, underneath the Configuration parent menu item.

See Conflicts for feature details.

Edit conflicts by using drag and drop to move jobs around within conflict groups, using their vertical ordering to indicate conflict priority. Remove jobs from conflict sets by dragging them into the Trash group.

Confirm your changes by clicking the Save button.

Adding and Removing Groups

Add new conflicts by clicking the Add New Group link in the All Jobs group. You can then use drag and drop to copy jobs from the All Jobs group into conflicted sets, or even move a job between conflicted sets. As of Obsidian 2.9.0, the same job can be copied into different conflict sets (see the note below on priority and conflict resolution).

Remove groups by clicking the Remove Group link in the conflict set.

Note: The order of jobs within a conflicted set indicates which job takes priority. Jobs at the top are given priority over those lower down, and will be executed first when conflicts arise. In addition, it is important to note that when selecting available non-conflicted jobs to run, Obsidian inspects the conflict sets in the order provided when they are saved (from left to right), and selects the highest priority available job before moving onto the next conflict set. When priority is significant and varies across different sets, ensure your conflict sets are in the desired order.