Skip to main content

Job and workflow statuses

In briefEvery job and every workflow instance carries exactly one status. A job's status says which gate it is at, or how it ended, and decides which of its 11 lifecycle actions it accepts. A workflow instance's status does the same for its own actions. This page lists every status, its family, and the actions each accepts.

WhereStatuses show on Operations › Processes: in the Status column of Job View and Workflow View, on the cards of the run diagram, and in each view's Status(s) filter as status groups. This page names each job status as the Job History report's Job Termination Status filter lists it (for example Waiting: Machine); the status badge on Processes spells some of them differently (Wait Machine) — see How each screen spells a status. A job's actions are in its row menu and on its detail panel's Status Update tab.

When

  • A job is waiting and you want to know what it is waiting for.
  • An action is disabled and you want to know why.
  • You need to know whether a status is final, or whether dependents have been released.
  • You want to run more work on a workflow instance that has completed.

Use something else when you need to decide what to do about a status: see the Operator response guide.

How

  1. Read the job's status on Processes.
  2. Find it under Job statuses to see what it means and which gate it is at.
  3. Check Which actions a job status accepts, then take the action from the row menu or the Status Update tab.

For the full steps, see Job statuses and actions.

Notes
  • The gates are checked in a fixed order, so a waiting status names the first thing still unmet.
  • A (Pending) status is not finished: dependents are released only when it settles.
  • Under Review is not final. It releases dependents waiting for a failure, but the workflow does not complete while a job holds it.
  • Skip in a live workflow is deferred: the job reads Job to Be Skipped until its turn comes.
  • Holding a workflow holds every sub-schedule beneath it, at any depth.
  • A workflow with failed jobs still completes as Completed. Workflow View marks it Completed with errors, with a red count of its failed jobs.
  • A job is never sent to an agent that cannot take it. It waits in Waiting: Machine, or a force-started job in Wait to Start (Forced), until its agent or a backup agent can, and its Status History says why it is waiting.
  • A job whose work no agent picks up does not wait for ever: it ends Initialization Error, or Missed Start Time when its Latest Start passes.
  • A job sent to its agent reads Start Attempted until the agent confirms the start, and only then Running. After about five minutes without a confirmation it reads Still Attempting Start; it is flagged, not failed.
  • Each run, retry, restart and force start is checked against late deadlines measured from its own start, so a job you restart after its deadline has passed is not reported late at once.
Watch out
  • Mark Finished OK and Mark Failed do not stop a running job. Kill it first if the work has to stop.
  • Cancel is not accepted on a running job. For a running job, use Kill.
  • Kill on a legacy job is refused when its agent's Allow Kill is off — the default on SAP R/3 and CRM agents.
  • A UNIX Command, SAP R/3 Job, SAP BW Process Chain, z/OS Batch Job or z/OS Started Task restarted on a step keeps that step, through failure retries, until it finishes OK. Restart it From the beginning to clear it.
  • Hold, Release and Start on a completed workflow reopen it. Nothing runs until you restart a job on it.
  • A running container job accepts no action, not even Kill: act on the jobs in its nested workflow instead.