Skip to main content

Exit codes and machine messages

In briefA finished job records an exit code, a termination description and, for a legacy job, an agent message. The exit code is the number the process or agent returned; the termination description says why the job ended; the agent message is a legacy agent's own reason when Termination holds the exit code instead.

WhereProcesses › a job › Summary tab, under Completion: Exit Code, Termination and Agent Message. The job grid and diagram call the exit code Return Code. Past runs are under Status History › Job Execution History, and every run is in Reports › Job History.

When

  • A job failed and you need to know why.
  • A job went to Initialization Error and never ran.
  • You want an event to fire on a particular exit code or reason.

To see how a status is decided, see Job and workflow statuses.

How

  1. Open the job on Processes and select the Summary tab.
  2. Read Termination first; on a legacy job, read Agent Message too.
  3. Look the text up in Termination descriptions to see who fixes it.
  4. Fix the cause, then restart the job.

The full steps are in Recover a failed run automatically.

Notes
  • — means no exit code: a job that failed with 0, or one that failed before anything ran.
  • A process ended by a signal, or by the one-hour limit, reports 128.
  • Windows, UNIX and SQL legacy jobs record the exit code as their termination description; IBM i jobs record a message ID such as SMA0036, SAP R/3 and SAP BW jobs the agent's text, such as 0 - 12345601, whose leading code is the exit code, and z/OS jobs the agent's text.
  • A machine that goes down holds its jobs rather than failing them.
Watch out
  • Every Universal Agent job stops at one hour, whatever it is doing.
  • A failure the relay raises before sending a legacy job ends in a code in brackets, such as (RC_NO_RUNAS_LOGIN): restarting without fixing the setting fails the same way.
  • An Exit Description event compares the termination description, not the exit code.