Respond to a failed connector job
- Synopsis
- Full Details
In briefWhen a connector job fails or stalls, read its Output and the Termination text first, then find the symptom in the table for its kind of job. Problems with the job's settings go to the Builder; problems with connections, agents, drivers or the relay go to the Administrator.
- On Run Command and Run Script, a matching exit criterion means failure, and with criteria set Fail on Error is ignored.
- Every Universal Agent job has a fixed one-hour limit; a job stopped at the hour reports exit code
128. - Database work runs through the SQL LSAM job types; their failures are in the legacy LSAM table.
- An IBM i job's Termination holds the message ID the agent reported; any failure text is in Agent Message.
- A z/OS job's Termination holds the agent's text; the agent decides its outcome from the job's condition-code or return-code range, and a z/OS Console Command finishes once the command is issued. An MCP job's agent decides from its fail codes, and an OS 2200 Job's from its Completion Status rules; for both, Termination is the agent's text too.
- Many legacy features need a current relay. An older relay can refuse a dispatch, or send a File Arrival job the wrong schedule date. A job carrying IBM i lists, z/OS pre-runs, Step Control rows or restart options, an MCP prerun, or an OS 2200 prerun or file dependencies is refused with RELAY_LSAM_FEATURE_UNSUPPORTED rather than run without them.
- Never include credentials when you escalate.
When a connector job fails or stalls, the job output almost always tells you what happened. Read it first, then use the tables below to act or route it to the right team. The Continuum Jobs tab covers the job types that run on a Universal Agent; the Legacy LSAM Jobs tab covers legacy LSAM machines.
Routing rule of thumb: problems with the job's settings go to the Builder; problems with connections, agents, drivers, or the relay go to the Administrator.
A connector job fails or stalls mid-run, and it's not obvious whether the fix belongs to the operator, the builder, or the administrator. It bounces between teams while the run waits.
- Continuum Jobs
- Legacy LSAM Jobs
Continuum Jobs
The job types that run on a Universal Agent, or on the platform itself.
- Commands and Scripts
- Internal Jobs
- File Waits
Commands and Scripts
Commands and scripts (Run Command, Run Script)
| Output / symptom | Meaning | What to do |
|---|---|---|
| "could not start" / command not found | The program or interpreter isn't on the agent | Builder confirms the command; Administrator confirms it's installed on the agent. |
| Script won't start (PowerShell/Python) | The interpreter isn't installed on the agent | Administrator installs the interpreter (e.g. pwsh, python3). |
| Failed with a non-zero exit code | The command/script reported an error | Builder checks the command and whether Fail on Error, or an exit criterion, should apply. |
| Failed, and the Termination text names an exit criterion or an output parsing rule | The job's configured failure criteria decided the outcome — not the command's exit code on its own | Read the Termination text: it names the rule that fired and the code it set. Builder adjusts the criteria (Run Command / Run Script). |
| Finished OK even though the output looks wrong | Exit criteria are configured and the code matched none of them. On these job types a matching criterion means failure, and the criteria replace Fail on Error entirely, so a code that matches nothing finishes OK | Builder adds a condition that matches the code. An over-narrow set lets real failures through. |
| A legacy job finished OK but the agent's own log says it failed | Its criteria table was evaluated by OpCon Continuum rather than by the agent, so the agent was given the platform default and reached the opposite conclusion | Read the Exit Criteria Evaluated entry on the job's Status History tab, which records the exit code, the row that matched (or that none did), the verdict and the status the agent reported. On a Windows, UNIX/Linux or SQL job the Termination text holds the exit code itself; on other types with no termination text of their own it reads Finished OK (Exit Criteria) Return Code='N'. Nothing is wrong. |
| A legacy job never starts, and the dispatch is refused on its exit criteria | The relay serving that machine predates Exit Criteria Result, range conditions, or tables of more than five rows, and refuses to send a table it can't represent | Administrator upgrades the relay. As a stopgap, Builder rewrites the table as up to five plain conditions with Exit Criteria Result Fail. |
| A legacy UNIX job that used to finish OK now fails on an output parsing rule | Its output parsing rules never reached the agent in earlier builds, so they were stored and never applied. They run now, and one of them matched | Nothing is broken — the rule is doing what it was configured to do, and the earlier Finished OK was wrong. Read the Termination text for the rule and the code it set; Builder reviews the rules (UNIX Command). |
| Ended after one hour, exit code 128 | The command ran past the fixed one-hour limit every Universal Agent job has, and was stopped | The limit can't be raised. Builder splits the work or makes the command finish within the hour. |
Internal Jobs
Internal jobs (Null Job, Workflow Container)
| Output / symptom | Meaning | What to do |
|---|---|---|
| Null Job sits waiting | Waiting on its dependencies (by design), or on hold | Operator checks predecessors; release if intentionally on hold. |
| Workflow Container stays running a long time | The embedded (nested) workflow hasn't finished | Open the nested workflow instance and troubleshoot it there. |
| Container failed: "No deployment found for workflow …" / "Circular workflow reference detected" / "Maximum nested workflow depth … exceeded" | The embedded workflow isn't deployed for the date or the reference is wrong, it loops back to an ancestor, or containers nest more than 10 deep | Builder fixes the workflow reference, deploys the workflow for the date, or flattens the design. |
| The build succeeded, but a warning says a Workflow Container has no sub-schedule to run | The container couldn't be expanded during the build — the parent still built, by design | Read the reason in the warning (or hover the warning icon on the container job), fix what it names — usually the embedded workflow isn't deployed for that date — then rebuild with overwrite. |
File Waits
File waits
For a Wait for File job that's stuck or timed out, see Respond to a stuck or failed Wait for File job. The job output names the exact criterion it's waiting on.
Legacy LSAM Jobs
Jobs that run on a legacy LSAM machine through the relay, grouped by the kind of machine. All Platforms holds what any legacy job can run into.
- All Platforms
- Windows
- UNIX/Linux
- IBM i
- SQL
- SAP R/3
- SAP BW
- z/OS
- MCP
- OS 2200
All Platforms
Legacy LSAM commands
| Output / symptom | Meaning | What to do |
|---|---|---|
| The job finds no agent to run on | The relay is down or the LSAM machine is unreachable | Administrator checks the relay and LSAM connectivity. |
| Legacy job rejected at dispatch, naming a missing login name, password, user, or group | The batch user connection the job runs as is incomplete | Administrator completes the connection — see Manage connections. |
| Legacy job rejected at dispatch: attached connection is not a … credential | The job's batch user is of the wrong platform's type | Builder re-picks the account in the job's Connection field. |
| Legacy job fails at dispatch: LSAM_AGENT_TYPE_MISMATCH: this job needs an agent of type …, but agent '…' … has type … | The job's machine name points at an agent of another type, such as a UNIX job aimed at a Windows agent | Builder points the job at an agent of the type the message names — see A legacy job aimed at an agent of another type. |
| Marked failed though it ran | An exit-criteria condition matched | Builder confirms the failure conditions match the program's real codes. |
| Kill on a legacy job is refused with does not allow its jobs to be killed | The agent's Allow Kill is off — the default on an SAP R/3 and CRM agent | The job keeps running. An Administrator can turn Allow Kill on for the agent. See Allow Kill. |
| Kill is unavailable on an OS 2200 or SAP BW job, with the reason Jobs on OS 2200 agents cannot be killed. (or SAP BW) | Jobs on those agent types cannot be killed, whatever Allow Kill says | Nothing to change; the job runs to its own end. See Allow Kill. |
| You Kill an MCP job and it stays at Job Running To Be Terminated | The MCP answered that it did not stop the job, which usually means the job had already finished. The job is not failed; it takes the outcome the MCP reports | Wait for the MCP to report how the job ended. See A kill the MCP refuses. |
| A legacy job reads Start Attempted, then Still Attempting Start with Start Delay Detected | The agent has not reported the job running: its relay is disconnected, or the LSAM machine is unreachable or has not started the job | Administrator checks the relay and the machine. The job is not failed for waiting: it moves on to Job Running when the agent reports it, or resolve it with Mark Finished OK, Mark Failed or Kill. See A job is Running only once its agent confirms it |
| Every job on one legacy agent sits Running with no completion, and the agent still reads as reachable | The agent stopped answering without disconnecting — a paused or frozen host, or a NAT port-forward holding the socket open. The relay now declares it down after 90 seconds of an unanswered acknowledgement; on an older relay the wait was about two and a half hours | Confirm the machine is actually up, and have the relay upgraded if it is not declaring the agent down. See When a legacy agent stops answering. |
| A File Arrival job watches a day either side of the one you authored | An out-of-date relay sends its own UTC date as the job's schedule date, so the window shifts for agents west of UTC | Have the relay upgraded — see The schedule date a legacy job is sent with. |
Windows
| Output / symptom | Meaning | What to do |
|---|---|---|
| A Windows - File Arrival job finishes OK although no file came, or fails although one did | Its exit-criteria table decided the outcome — Continuum applies it to the watcher's exit code (1 is no file in the window) | Builder checks the job's Exit Criteria and Exit Criteria Result; the Exit Criteria Evaluated entry on the job's Status History tab shows which row matched. |
| A Windows - File Arrival job is refused at dispatch naming its file name's double quotes | The quotes in File Name are unbalanced, leave more than one path (a space outside the quotes with more after it), or stand for a literal quote. On a relay older than the current release, any double quote is refused | Builder fixes the quoting so the name reads as one path, or has the relay upgraded. See Quotes in the file name. |
UNIX/Linux
| Output / symptom | Meaning | What to do |
|---|---|---|
| UNIX job rejected at dispatch, naming a missing user or group | A UNIX job must name a batch user, and none is attached | Builder attaches a UNIX Batch User connection. |
A UNIX job ends with exit 127 and the log shows quot: not found (or amp, lt, gt, apos) | An older relay converted the quotes and ampersands in the command into their XML forms, and the UNIX agent ran that text literally | Have the relay upgraded — current relays send UNIX values unaltered. Until then, move the command into a script on the machine and run that. |
A UNIX job is rejected at dispatch naming a field code, for </F> or <F I= | A UNIX value can't carry either sequence — the agent would read it as part of the message rather than as the value | Builder removes it; put those characters in a script on the machine instead. |
| A UNIX - File Arrival job is rejected at dispatch naming the file name | The path holds a character the relay refuses anywhere — ``` ` $ " \ ; | & < > ( ) ' ``` — or a space in its directory part, or is over 255 characters. Continuum refuses these on any agent, because an older UNIX agent hands the name to a shell when it searches |
A UNIX - File Arrival job fails with exit code 2 | The directory being watched does not exist on the agent. Only the file-name part takes wildcards; the directory part is literal and has to be there already | Create the directory on the machine, or correct the path. |
IBM i
| Output / symptom | Meaning | What to do |
|---|---|---|
| An IBM i job is refused at dispatch naming a list, a row and a column | A message-monitor, spool-file or dynamic-variable row breaks its rules, a list holds more than 99 rows, or a Restricted Mode job carries a message or spool list | Builder fixes the row the message names. See IBM i lists. |
| An IBM i - File Arrival job is refused at dispatch naming the file name, the window or the batch user | The File Name is missing or holds a control character such as a tab or line break, the window end is earlier than its start, or an authority check is on with no batch user. A relay older than the current release also refuses & ' < > and " in the File Name | Builder fixes the field the message names; for those five characters, have the relay upgraded. See IBM i - File Arrival. |
| An IBM i - File Arrival job ends before a file that arrives later | With no re-check interval the agent checks for the file once | Builder adds a $@RECHKFREQ dynamic variable and sets the window end. |
An IBM i job's Termination shows SMA0036 or SMA0037 | That is the message ID the agent reported — finished OK, or failed — and it is the job's Exit Description. Any failure text the agent sent is in Agent Message | Nothing is wrong. A Builder who wants to key off the ID enters it as an Exit Description event's Value, such as Equal To SMA0037. See The message ID is the job's Exit Description. |
| An IBM i job with message monitors, spool files or dynamic variables goes to Initialization Error with RELAY_LSAM_FEATURE_UNSUPPORTED | The relay serving the machine has not reported that it can send them, so the job is refused rather than run without them | Administrator upgrades the relay. |
SQL
| Output / symptom | Meaning | What to do |
|---|---|---|
| An MS SQL Script job fails reaching the database, after dispatching cleanly | Encrypt Connection is on (the default) and SQL Server has no certificate the machine trusts | Administrator installs a trusted certificate, or the Builder turns Encrypt Connection off. |
| An MS SQL Script job is rejected at dispatch naming its script | Neither SQL Script Statements nor Script File Path is filled in, or both are | Builder supplies exactly one of the two — setting Script Source shows only the one it uses. |
An MS SQL Script or Other DB job is rejected at dispatch naming scriptSource | Its Script Source disagrees with the script field that is filled in — a job written outside the job editor | Builder opens the job and sets Script Source to match, or fills in the field it names. |
| An MS SQL Script job's own result is ignored | Use Exit Code From Script Result has no effect when the script comes from Script File Path | Builder moves the script inline, or judges the outcome from the reported exit code. |
| An MS SQL Job job reports Finished OK while the SQL Server Agent job is still running | Its Monitoring End Time was reached, which reports success and leaves the SQL job running. An end time already in the past does this immediately | Builder sets Monitoring End Time to day 0 / 00:00 to watch until the job completes. See MS SQL Job. |
| An MS SQL Job job is refused at dispatch naming a batch user | MS SQL Job requires a SQL Batch User connection; it has no run-as-the-service-account mode | Builder attaches one. |
| An MS SQL Job job fails and its exit code is not a program's | The codes are the SQL Server Agent job's own outcome — 1 Failed, 2 Retry, 3 Cancelled, 4 In progress or monitoring error, 5 Unknown, -1 a monitoring error. Without exit criteria only 0 finishes OK | Builder reads the code against that list, and adds an exit-criteria table if another code should count as success. |
An MS SQL DTExec job fails with return code 4, 5 or 6 | DTExec could not find the package (4), could not load it (5), or hit a syntax or internal error (6) | The job's output is DTExec's own and says which; Builder corrects the Package Location, Package Path or Other Options. See MS SQL DTExec. |
| An MS SQL DTExec job is refused at dispatch naming the batch user | Its package is on the file system, which always runs as the agent's service account, and the job still names one — a job written outside the job editor, which hides and clears Connection for the file system | Builder opens the job, switches Package Location away from File system and back to clear it, and saves. |
| An MS SQL DTExec job goes to Initialization Error with RELAY_LSAM_FEATURE_UNSUPPORTED naming configuration files | The job has a Configuration File, and the relay serving the machine has not reported support for it | Administrator upgrades the relay; or Builder clears Configuration File and puts the path in Other Options as a /ConfigFile switch. |
An MS SQL DTExec job is refused at dispatch naming configFile | The Configuration File holds a double quote, ends with a backslash, is too long with Other Options, or is set while Other Options already has a configuration-file switch | Builder fixes the path, or keeps only one of the two. See The configuration file. |
| An Oracle, Other DB or MySQL job never starts: the dispatch is refused as an unsupported job type | The relay serving the machine predates these job types | Administrator upgrades the relay. |
| An Oracle job is refused at dispatch naming a field or the batch user | No batch user or no password on it, a missing path, server or service name, inline SQL left on the job, or a character the SQL*Plus command line cannot carry | Builder fixes the field; Administrator fixes a refused login or password on the connection. See Oracle. |
An Oracle job fails with return code 1017, or another number | The code is the ORA error number — 1017 for an invalid user name or password, 942 for ORA-00942 — and 1 means the script file is missing | Administrator corrects the credential for 1017; otherwise read the job output for the Oracle error. |
| An Other DB job is refused at dispatch naming its connection string | The string names a password, secret, token or login key, even inside a quoted value, or a brace or quote is never closed | Builder removes the key and attaches a SQL Batch User for the login. See Other DB. |
| An Other DB job fails with no return code | The connection did not open — the driver, provider or DSN is not installed on the agent, or the server or login is wrong | Read the driver's message in the job output; Administrator checks the driver or DSN on the machine. |
| A MySQL job is refused at dispatch naming a field or the batch user | No batch user or no password on it, a missing script path, server or database name, inline SQL left on the job, a user variable the mysql client cannot take, or a character the Windows command line cannot carry | Builder fixes the field; Administrator fixes a refused login or password on the connection. See MySQL. |
A MySQL job fails with return code 1 or 255 | 1 is any MySQL error, a failed login or connection, or a missing script file; 255, on a job with user variables, means the mysql client is not installed or not on the machine's PATH (without user variables that also returns 1) | Read the mysql client's message in the job output; Administrator checks the credential and the client on the machine. |
| An MS SQL Job job fails reporting it cannot see or start the SQL job | The batch user has no rights to the job in msdb | The SQL Server administrator grants the account rights to the job — SQLAgentOperatorRole for a job it does not own. |
SAP R/3
| Output / symptom | Meaning | What to do |
|---|---|---|
An SAP R/3 Job fails with exit code 70006, and Termination starts 70006 | The SAP job with that name and number does not exist, or is not in Scheduled or Ready status | Builder checks the name and number in SM37, or runs Check SAP Job Numbers to find every SAP R/3 Job whose stored number SAP no longer has and correct it. See What the job reports. |
| An SAP R/3 Job fails at dispatch with RELAY_LSAM_PLATFORM_UNSUPPORTED | The relay serving the agent predates the SAP R/3 Job type | Administrator upgrades the relay. |
| Restart selected on a job's Child Processes is refused with The child processes changed while you were restarting or Some selected child processes are no longer on this job | The agent reported a change to the children after you selected them | Reload the job, select the failed children again and restart. See Restarting only the failed child processes. |
SAP BW
| Output / symptom | Meaning | What to do |
|---|---|---|
An SAP BW Process Chain job fails with Termination 1 - NOT FOUND | SAP does not know a process chain by that name | Builder checks the technical name in RSPC. See What the job reports. |
| An SAP BW Process Chain job is refused at dispatch naming processChainName | The name is missing, over 25 characters once its tokens are resolved, or holds a character outside Windows-1252 | Builder fixes the Process Chain Name. See What is refused at dispatch. |
| An SAP BW Process Chain job fails at dispatch with RELAY_LSAM_PLATFORM_UNSUPPORTED | The relay serving the agent predates the SAP BW Process Chain type | Administrator upgrades the relay. |
z/OS
| Output / symptom | Meaning | What to do |
|---|---|---|
| A z/OS Batch Job is refused at dispatch with z/OS field … must be 1-8 characters (A-Z, 0-9, @, # or $) and must not start with a digit | A member, DD, user ID or system name is not a valid z/OS name once its tokens are resolved | Builder fixes the field the message names. See What is refused at dispatch. |
| A z/OS Batch Job is refused at dispatch with z/OS field memberName is blank and the job name does not give a valid z/OS member name; set Member | Member is blank and the start of the job's name is not a valid member | Builder sets Member. See The member a blank Member submits. |
| A z/OS Batch Job fails at dispatch with RELAY_LSAM_PLATFORM_UNSUPPORTED | The relay serving the agent predates the z/OS Batch Job type | Administrator upgrades the relay. |
| A z/OS Batch Job reads Prerun Active | The agent is running the job's prerun — or waiting on its Dataset Pre-run rows; the job moves on to Job Running when the job itself starts | Nothing, unless it stays there past its Late to Finish time; Kill it if it should not wait. See Dataset Pre-run. |
| A z/OS job with Dataset Pre-run rows, Step Control rows or Restart options goes to Initialization Error with RELAY_LSAM_FEATURE_UNSUPPORTED | The relay serving the machine has not reported that it can send them, so the job is refused rather than run without them | Administrator upgrades the relay. |
| A z/OS job with Message, Job/Task, Tape or REXX Pre-run goes to Initialization Error with RELAY_LSAM_FEATURE_UNSUPPORTED | The relay serving the agent has not reported that it can send those pre-runs | Administrator upgrades the relay. See Message, Job/Task, Tape and REXX Pre-run. |
| A z/OS job is refused at dispatch naming messagePrerun, jobTaskPrerun, tapePrerun or rexxPrerun | A pre-run breaks its rules — a message key over 44 characters, two message rows that repeat each other, tape units with no device, or a REXX DD or parameters with no procedure name, for example | Builder fixes the pre-run the message names. See What is refused at dispatch. |
| A z/OS Batch Job is refused at dispatch naming datasetPrerun | A Dataset Pre-run row breaks its rules, or two rows repeat each other | Builder fixes the row the message names. See Dataset Pre-run. |
| A z/OS Batch Job's Output tab says This z/OS job's output can't be listed: its agent did not report where the job's output is for this run… | The agent did not report where it filed this run's output, or the run predates the relay's upgrade | Read the output on the mainframe. See Its output. |
| A z/OS Batch Job's Output tab says This z/OS job is still running and its agent has not yet reported where its output is | The agent reports it at the latest when the job ends | Open the tab again later. |
| A job's Output tab says JORS port not configured for agent: … | The agent's JORS Port is empty, which is where a z/OS agent starts | Administrator sets the agent's JORS Port. See Agents and agent pools. |
| A z/OS Started Task, REXX Exec or Console Command fails at dispatch with Unsupported z/OS task type for TX1 translation | The relay serving the agent predates the job type | Administrator upgrades the relay. |
| A z/OS job is refused at dispatch with z/OS field … is not used by a … job; remove it | The job carries another z/OS job type's field, left by an edit on the Code tab or through the API | Builder removes the field the message names. See What all three share. |
| A z/OS REXX Exec or Console Command restarted on a step is refused with restart on step is not available for this kind of z/OS job | Only a z/OS Batch Job or Started Task restarts on a step | Restart it from the beginning. See Restarting it. |
| A z/OS Tracked Job or z/OS Queued Job fails without reaching the agent, with … runs only after its agent reports it … (RC_LSAM_PRIVATE_DATA_REQUIRED) | The job started from its workflow before the agent reported it, so there was nothing to send | Builder checks the job: it runs only from the agent's report. See z/OS Tracked Job and z/OS Queued Job. |
| A job the z/OS agent tracks or queues never appears in its workflow | The agent's report was refused — the workflow is not built for that date, or the job is not on it or is not a Tracked or Queued Job — and the agent was told why | Builder checks the job and the workflow instance. See Tracked and queued jobs. |
| A z/OS job restart is refused with the start or end step is not one of the steps this job reported | The range names a step the agent did not report, typically from an event | Restart from the dialog, which offers only reported steps. |
| The JCL dialog says The save may or may not have been applied. Load the member again to check. | The JCL was sent and no answer Continuum can trust came back | Load the member to see what it holds before saving again. See Viewing and editing JCL. |
| The JCL dialog says JCL cannot be viewed or saved for this agent because it uses TLS for scheduling. | The agent has Use TLS for Scheduling on, and JCL access is not available over TLS | Jobs on the agent still run. See Use TLS for Scheduling. |
| The JCL dialog says You have no z/OS user id assigned. Ask an administrator. | No z/OS user ID is assigned to you | Administrator assigns one on the z/OS User IDs tab of the Permissions page. |
MCP
| Output / symptom | Meaning | What to do |
|---|---|---|
| An MCP job is refused at dispatch with MCP job has no batch user attached; select a Batch User | The job names no Connection | Builder picks an MCP Batch User. See MCP Run and MCP Start. |
| An MCP job is refused at dispatch with MCP field … (RC_INVALID_MCP_FIELD) | A value breaks its field's rules once its tokens are resolved | Builder fixes the field the message names. See What is refused at dispatch. |
| An MCP job fails at dispatch with RELAY_LSAM_PLATFORM_UNSUPPORTED | The relay serving the agent predates the MCP job types | Administrator upgrades the relay. |
| An MCP Copy, MCP Change or MCP Remove job fails at dispatch with Unsupported MCP task type … (RC_MCP_UNSUPPORTED_TASK_TYPE) | The relay serving the agent runs MCP jobs but predates these three types | Administrator upgrades the relay. See MCP Copy, MCP Change and MCP Remove. |
| An MCP or OS 2200 job sits in Prerun Failed and starts again every few minutes | Its prerun failed, or on OS 2200 a file dependency is not met, so the job is re-attempted rather than failed | Fix what the prerun or file checks, or Cancel or Skip the job. See A prerun that fails is re-attempted. |
| An MCP job with a prerun, or an OS 2200 Job with a prerun or file dependencies, goes to Initialization Error with RELAY_LSAM_FEATURE_UNSUPPORTED | The relay serving the machine has not reported that it can send them, so the job is refused rather than run without them | Administrator upgrades the relay. |
| An MCP job's Output tab says This MCP job's output can't be listed: OpCon has no record of where the agent filed it… | The agent did not report where it filed the output, and there is no status description to take the mix number from — it has not reported its status yet, or ran before the relay was upgraded | Open the tab again later, or read the output on the MCP system. See Its output. |
OS 2200
| Output / symptom | Meaning | What to do |
|---|---|---|
| An OS 2200 Job is refused at dispatch with OS 2200 field … (RC_INVALID_OS2200_FIELD) | A value breaks its field's rules once its tokens are resolved, or was set by a change to one run or by a transformation rule, which saving does not check. The editor refuses any other invalid value when the workflow is saved | Builder fixes the field the message names. See What is refused, at save and at dispatch. |
| An OS 2200 Job fails at dispatch with RELAY_LSAM_PLATFORM_UNSUPPORTED | The relay serving the agent predates the OS 2200 Job type | Administrator upgrades the relay. |
| An OS 2200 Job finished with a result you did not expect | No Completion Status row matched and Anything Else decided, or a Value was entered in octal rather than decimal | Builder checks the rows. See Completion Status. |
| An OS 2200 Job's Output tab says This OS 2200 job's output can't be listed: its agent did not report where the job's output is…, or that the job is still running and its agent has not yet reported where its output is | Continuum can list the output only where the agent reports it | Open the tab again later, or read the output on the OS 2200 system. See Its output. |
When you escalate
Include the job output, the job type, and (for database or LSAM jobs) the connection or machine name involved, but never credentials. Note whether the same operation works when run directly (in a terminal, a database client, or on the LSAM machine).
Related topics