Skip to main content

Order jobs with dependencies

In briefA job runs only when all of its dependencies are satisfied. A Job dependency waits on another job's result, or with Conflict keeps two jobs from running at once; a Threshold dependency waits on a threshold's value, a Resource dependency on free units, and an Expression dependency on an expression that renders True. You add them on the job editor's Dependencies tab.

Notes
  • Requires waits when the predecessor isn't in the run for the date; After proceeds without it. Conflict takes no Condition.
  • Any means a success or a failure result. A cancelled predecessor, or one that missed its start time, satisfies no Condition.
  • Inside a workflow built as several schedule instances, a dependency resolves within the same instance. A resource spans instances.
Watch out
  • A Requires dependency on a predecessor that never comes waits indefinitely. Use After for an optional predecessor.
  • An expression that renders anything other than True or False, including a number, puts the job on hold.
  • A job can't depend on itself at a Days Offset of 0; the save is blocked.