Operator response guide
- Synopsis
- Full Details
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
- Find the job's status in Situation → response.
- For a failed job, read its Output, and the Exit Code and Termination rows in Summary › Completion.
- 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.
- 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.
- 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.
Guides an operator through the daily run. See How the daily run works and Job and workflow statuses.
Task walkthrough: Respond to a failed job. This page is the full configuration and troubleshooting reference.
Most of what an operator does during the daily run is read a status and decide whether it needs a response. This page maps each situation you are likely to meet to what it means and the action to take, then covers responding to a failed job, reading its exit code, and when to escalate.
Situation → response
| Situation | What it means | Action |
|---|---|---|
| Job in Waiting: Job Dependency, Waiting: Threshold Dependency, Waiting: Resource Dependency or Waiting: Expression Dependency | Waiting on a predecessor job, threshold, resource, or expression | Confirm the blocker; if it should proceed now, Force Start. If it shouldn't run, Skip. |
| Job in Waiting: Machine | No agent/machine available — a specific-agent job holds here while its target agent cannot take it (offline, marked, not found, or its status cannot be checked), and a Universal Agent pool job while its pool has agents and none of them is online | Check agent/relay availability (Administrator); the job proceeds when the target is back online. The job's Status History has an Agent Availability Hold entry that says why it is waiting. A legacy agent showing Unknown (yellow) usually means its relay has gone stale, or the relay cannot tell whether the agent is reachable — check the relay first. |
| Job in Waiting: Start Time | Not yet at its start time | Normal; Force Start only if it must run early. |
| Job in a running state (Running, Pre-run Active, starting, Late to Finish) | Actively running | To stop it, use Kill — Cancel applies only before a job starts running. To force its downstream outcome, Mark Finished OK or Mark Failed (a running container job accepts none of these: act on the jobs in its nested workflow). |
| Job On Hold | Held intentionally | Release when ready. |
| Job Late to Start / Late to Finish | Past its late deadline: not yet started (Late to Start), or still running (Late to Finish) | Investigate the delay. Neither status stops the job; it can still start, or still finish with its own outcome. |
| Job Failed | The job failed | Read the job output/logs; Restart once fixed, Mark Fixed if resolved outside the system, Under Review to flag it, or Cancel. |
| Job Missed Start Time | Didn't start by its Latest Start deadline | Force Start it if it must still run, or Skip or Cancel it if it should not. |
| Job stuck in a (Pending) status, such as Finished OK (Pending) | Completion processing not settling | Transitional normally; if prolonged, escalate (see below). |
| Workflow On Hold / Parent Hold | Held (or parent held) | Release when ready; releasing the parent releases children. |
| Workflow Completed, but a job in it has to run again | The run finished; you need more work out of that same instance rather than a fresh build | Hold, Release or Start the completed instance to reopen it, then Restart the job. Nothing runs on the reopen alone. A nested sub-schedule can't be reopened — act on its parent. |
| Workflow Started by User with nothing running | An instance reopened with Start on which no job has been revived yet | Restart the job you reopened it for, or Close the instance to put it back to completed. |
Responding to a failed job
To respond to a failed job, complete the following steps:
- Open the job's detail and read its output/logs to find the cause.
- Resolve the cause (often a connector/config issue — route to the Builder or Administrator).
- Then choose: Restart (re-run), Mark Fixed (resolved outside the system), Under Review (flag for follow-up), or Cancel (abandon).
Reading the exit code
A completed job's detail shows its Exit Code (return code) and a Termination description in the Summary tab's Completion section, and the Output tab's header shows the Exit Code beside the run's date. In Completion the Exit Code is a badge: green for 0, red for any other value. It is a data field only — it does not decide the job's status (a job can be Failed with its exit code shown).
- A real numeric code is shown, including
0. - A job with no numeric code reported shows
—on the Output tab and has no Exit Code row in Completion — never a stand-in0— so "failed with code 0" and "failed, code unknown" read differently.
Which action is available
Actions are status-gated (see Job and workflow statuses). There are 11 job actions. A job's row menu lists all of them and disables the ones its status does not accept; its Status Update tab lists only the ones it accepts. Key points for triage:
- Cancel stops a job that hasn't started running; Kill stops one that is running. They don't overlap — offer Kill, not Cancel, for anything in a running status.
- Restart is available from any stopped state (Failed, Marked Failed, Cancelled, Skipped, Initialization Error, Under Review, Job to Be Skipped, and the finished states) — not only Failed or Cancelled.
- Mark Fixed from Failed, Marked Failed, Initialization Error or Under Review; Release only from On Hold; Force Start from held, waiting and Missed Start Time jobs; Skip from the same, except Job to Be Skipped, and from failed and under-review jobs.
- Skip is deferred and in-sequence. In a live workflow, Skip marks the job Job to Be Skipped rather than skipping it on the spot: it becomes terminal Skipped — and its dependents are released — only when it would otherwise have been its turn to start (its start time, job, threshold and resource gates satisfied). Skipping a job that has already reached that point (Failed, Missed Start Time) resolves promptly. So after selecting Skip, expect the job to sit in Job to Be Skipped until its turn comes — that is normal, not a stuck action.
- Mark Finished OK / Mark Failed are broad manual overrides that force a job's outcome so dependents proceed/react; accepted from most statuses, including some finished ones. A running container job accepts neither, and Kill is refused on any container job: its outcome follows its nested workflow.
- Marking a running job doesn't stop it. Both overrides move the status the platform records and nothing else — the process carries on running on the agent until it finishes by itself. Kill is what stops the work. Mark a running job and then restart it and you can have two runs of the same program alive at once, so Kill first if the work has to stop too. See Marking a running job does not stop it.
- Kill on a legacy job can be refused by its agent. When the agent's Allow Kill is off — the default on an SAP R/3 and CRM agent — or the agent is an SAP BW, OS 2200 or BIS agent, the kill is refused and the job keeps running. See Allow Kill.
If an action is disabled in the row menu, or missing from the Status Update tab, the job isn't in a status that accepts it.
Contact support when
- A job sits in a (Pending) status, such as Finished OK (Pending), indefinitely.
- A status-appropriate action is rejected by the system, or a job's status doesn't reflect what the agent actually reported.
Include the workflow instance, the job, its status, and the job output.