Skip to main content

Operator response guide

In briefMost of an operator's day is reading a status and deciding whether it needs a response. This guide maps each situation you are likely to meet to what it means and the action to take, then covers a failed job, its exit code, and when to contact support.

WhereYou act on Operations › Processes: a job's row menu or its detail panel's Status Update tab for the action, and its Output and Summary tabs for what happened.

When

  • A job is waiting, held, late or failed, and you need to decide what to do.
  • A job failed and you need to read why before you act.
  • An action you expected is disabled.
  • A completed workflow has to run a job again.

Use something else when you need the full list of statuses and the actions each accepts: see Job and workflow statuses.

How

  1. Find the job's status in Situation → response.
  2. For a failed job, read its Output, and the Exit Code and Termination rows in Summary › Completion.
  3. Fix the cause, then take the action from the row menu or the Status Update tab.

For the full steps, see Respond to a failed job.

Notes
  • Cancel is for a job that has not started running; Kill is for one that has.
  • Skip in a live workflow is deferred: the job reads Job to Be Skipped until its turn comes.
  • The exit code is a data field. It does not decide the job's status.
Watch out
  • Mark Finished OK and Mark Failed do not stop a running job. Kill it first if the work has to stop, 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 job that stays in a (Pending) status is not settling: contact support.