Skip to main content

Job statuses and actions

In briefA job's status tells you which gate it is waiting at, or how it ended, and decides which of its 11 actions it accepts. Read the status on Processes, then act from the job's action menu or its detail panel's Status Update tab.

Notes
  • The action menu lists every action and disables the ones the status refuses.
  • Cancel is for a job that hasn't started running; Kill is for one that has.
  • Skip in a live workflow takes effect in sequence: the job reads Job To Be Skipped until its turn comes.
  • A job with failure retries left waits in Wait Start Time, not Failed.
  • Force Start skips what a job is waiting on, but not its agent: a force-started job waits in Wait To Start Forced until its agent or a backup agent can take it.
  • Exceeded Max Run Time and a Late to Start badge sit beside the status; neither changes it.
  • A job reads Job Running only once its agent confirms the start. Until then it reads Start Attempted, and after about five minutes Still Attempting Start.
Watch out
  • Mark Finished OK and Mark Failed don't stop a running job. Kill it first, or a restart can leave two runs of it alive at once.
  • A running container job accepts no action, not even Kill: act on the jobs in its nested workflow instead.
  • A cancelled job satisfies no job dependency on it, so its dependents keep waiting.
  • A job whose Latest Start passes while its workflow is held is ended as Missed Start Time on the first pass after you release it.