Manage agents and agent pools
- Synopsis
- Full Details
In briefAgents run your jobs, and agent pools route work to whichever agent is available. The Agents page holds every agent, pool and relay, and lets you mark an agent out of service for maintenance. A Universal Agent pool is a queue its agents claim work from; a legacy agent group is a set of legacy agents of one type that a legacy job can target.
- A pool job goes on the pool's queue once, and the first agent to ask for it runs it. A job for one specific Universal Agent can be taken by any agent in that agent's pool.
- A Universal Agent obeys its own
MAX_CONCURRENT_JOBSsetting (50 unless changed), not the cap shown on its row. - Unknown on a legacy agent means its relay can't vouch for it, not that the agent is down.
- A mark survives a reconnect and holds jobs that target the agent; Clear Mark releases them.
- Mark Offline stops communication with the agent, and Clear Mark opens a new connection; Mark Draining keeps it connected.
- Register a Universal Agent through the API; the install commands New Agent shows for Universal don't register it. A new one reads Offline until its program first checks in.
- Machine Properties on an agent's Edit Agent dialog holds that machine's own values, read
by
[[MI.Name]]. They are not encrypted.
- A legacy agent's Default event environment left unset means every event that machine raises is lost.
- A legacy agent with no FT Role takes part in no file transfer.
- A pool can't be deleted while it has agents.
- Agents and Agent Pools permissions count only under All workspaces; a grant confined to particular workspaces hides the tab.
- Allow Kill is off by default on an SAP R/3 and CRM agent, so its jobs cannot be killed until you turn it on.
- Use TLS for Scheduling never falls back to an unencrypted connection: an agent whose own TLS is off stays offline.
Agents run your jobs; agent pools group agents so work can be routed to whichever one is available. As an administrator you keep agents healthy and organized so workflows always have somewhere to run.
If workflows target a single named machine, one agent going down or filling up stalls the work. No one has a clear view of which agents are healthy or overloaded.
Where agents, pools and relays live
Select Agents in the navigation. The page has three tabs:
- Agents — every agent, Universal and legacy, in one table, with its relay, platform, running jobs, status, version, whether it uses TLS for scheduling, and last heartbeat.
- Agent Pools — Universal Agent pools and legacy agent groups in one table, told apart by Type.
- Relays — your relays; see Manage relays.
Select a row to open it. Each row's menu has the rest of its actions, and selecting several rows offers Delete for all of them. See The Agents area for every column and action.
An agent in use can't be deleted. Before it deletes an agent, Continuum checks that the agent is offline or Marked Offline, has no jobs waiting or running on it, and is not named by a workflow or by an unfinished job in any environment. A refused delete lists the reasons and the workflows and jobs that use the agent; clear them and delete it again. See An agent in use cannot be deleted.
Each tab and action follows your roles. A tab is shown only when your roles grant its View permission — Agents View, Agent Pools View or Relays View — under All workspaces, and an action you may not take is unavailable, with a tooltip that says why. Adding a Universal Agent to a pool, or removing one, needs Agents Edit as well as Agent Pools Edit, because it moves the agent; creating a legacy agent needs Relays View for its relay picker. See Agents, agent pools and relays are checked.
- Pools and Agents
- Agent State
- How Workflows Pick an Agent
- Manage Legacy Agents and Groups
- Troubleshooting
Pools and Agents
Agent pools
Group related agents into a pool, then let workflows target the pool instead of a single machine. To create one, complete the following steps:
- On the Agent Pools tab, select New Agent Pool.
- Enter a Name and choose a Type: Universal for Universal Agents, or a legacy type for
a legacy agent group. Neither can be changed later. A Universal Agent pool's name takes
lowercase letters, digits and
-, starting with a letter or digit; a legacy group's name takes letters, digits,.,_and-. Either can be up to 255 characters. - Optionally, add a Description, and use Add Agent(s) to Pool to pick agents of that type, then Commit Selected Agents.
- Select Save. The pool is created with its agents.
To change a pool, select it. Edit Agent Pool saves the description with Save, but adding, removing or deleting its agents takes effect immediately.
- A Universal Agent is in one pool at a time. Adding it to a pool moves it there, and it starts
taking that pool's work at its next sign-in refresh — up to about 15 minutes later. Remove from
Pool moves it to the pool named
default-cloud, and is offered only when such a pool exists. - A legacy agent can be in several groups of its own type; adding it to one leaves the others alone.
- A pool can't be deleted while it has agents. Remove or delete them first. Deleting a legacy group never deletes its agents.
The Running Jobs/Concurrent Jobs (max) column shows the work a pool's agents have claimed or are running now, over their caps added up. Work still waiting on the pool's queue isn't counted — the Agent-pool job queue dashboard widget shows that. Online counts only agents that can take work, so marked agents aren't included.
A pool doesn't pick an agent for a job. The job goes on the pool's queue and the first agent to ask for work takes it — see How workflows pick an agent. Because of that, a least-tasked pool job shows the pool as its agent while it is queued and running, and the agent that ran it once it completes.
Add a Universal Agent
Don't use the install commands that New Agent shows when you choose Universal. They don't
work in this build: the agent program has no configure or install command, and it doesn't
register itself when it first connects.
A Universal Agent is registered through the API, which returns the credential the agent signs in with. You then put that credential in a file on the agent machine, point the agent at the platform and start it. The steps, the file format and the agent's settings are in Registering a Universal Agent.
Set an agent's machine properties
Give a machine its own values, such as the address of the team that owns it or the path to a
runtime installed there, and jobs read them with [[MI.Name]].
- On the Agents tab, open the agent's Edit Agent dialog.
- Select Machine Properties in the footer.
- Select Add Property, and enter a Name and a Value. Change or remove other rows as needed.
- Select Save.
Verify: Machine properties saved. appears, and reopening Machine Properties lists the row.
You need Agents Edit under All workspaces to save; without it the list is read-only. Names are unique ignoring case, and an agent holds at most 200. Values are not encrypted, so don't store a credential here. The rules, and where each token form resolves, are in Machine properties.
Agent State
Read an agent's state
The Agents tab shows the essentials you need at a glance, and selecting a Universal Agent opens its read-only details:
- Status: Online, Offline, or Unknown. Unknown (shown yellow) applies to a legacy agent whose relay can't be reached, or whose relay reports that it can't tell whether the agent is reachable, so its state can't be confirmed. This is different from Offline, which means the agent itself is down. If someone has deliberately taken the agent out of service, the status reads Marked Offline or Marked Draining instead, or for example Offline (Marked Draining) once a drained agent has also gone down — hover it for the reason, who set it, and when. Marked Offline always reads alone. (Busy and Draining are in the status list, but nothing sets them in this build.)
- Version and Scheduling TLS: the version the agent reports — for a legacy agent, the one its LSAM reports — and whether Use TLS for Scheduling is on (— where the type can't use it).
- Last heartbeat: when it last checked in. Not communicating means Mark Offline has stopped communication with it. On a legacy agent, "Never" means its relay hasn't reported it yet. On a Universal Agent it means the agent program hasn't checked in since the agent was registered: a new Universal Agent reads Offline until it does.
- Platform: Universal, or the legacy type. A Universal Agent's details add its operating system.
- Running Jobs/Concurrent Jobs (max): the jobs it has claimed or is running now, over its cap. A
Universal Agent's cap reads 1, and it isn't the one the agent obeys — the agent runs up to its own
MAX_CONCURRENT_JOBSsetting (50 unless changed), so change that on the agent machine. A legacy agent's figure is the Concurrent Jobs (Max) on its edit dialog; it is not enforced, so it does not hold the agent's jobs back. - Runtimes: detected tools (Node, Python, .NET, Java, PowerShell), useful for the Run Script job. Docker is reported separately.
Take an agent out of service for maintenance
Patching a host, rebooting it, or holding a misbehaving machine back are all decisions the platform can't infer from a heartbeat — so you tell it directly. From the agent's row menu on the Agents tab — Universal and legacy agents alike:
- Choose Mark Draining to stop new work reaching the agent while it stays connected and jobs already on it finish, or Mark Offline to stop communicating with it entirely.
- Add a Reason — optional, but it's what the next person sees when they hover the status. If jobs are currently running, you're told how many. That's a warning, not a block: with Mark Offline they keep running, and their results are collected when communication resumes.
- When the work is done, choose Clear Mark. If communication was stopped, a new connection is opened. The agent's status goes back to reporting its actual connectivity.
A mark is yours, not the platform's: reconnecting doesn't clear it, and a heartbeat never overwrites it. While a mark is in place:
- No new jobs are sent to the agent, and it isn't picked as a pool or group member.
- A job that targets it waits rather than failing, and runs once you clear the mark — unless it names a backup agent that can take it, in which case it runs there.
- Force start is refused for a job aimed at a marked agent, naming the agent and your reason — unless one of the job's backup agents could take it instead. A force start that is accepted still waits in Wait to Start (Forced) until the agent or a backup can take the job. Aimed at a legacy agent group whose every usable member is marked, it is refused with Cannot force-start: no unmarked member of the target legacy agent group is available. Clear a mark to proceed., which names no agent. Clear the mark instead — there's no override. Force start is also refused for a job aimed at a legacy agent group that has nothing to dispatch to at all — an empty group, one whose members are all Unknown, or one with no online member holding a relay dispatch pool — and the refusal names which of those it is.
- Pool and dashboard counts stop calling it available, so a fully drained pool no longer reads as fully online.
Mark Offline stops communication; Mark Draining doesn't. Within about a minute of Mark Offline, the relay closes a legacy agent's connection and opens no other while the mark stays, so another scheduler can take the machine; a Universal Agent stops asking for work and checks back now and then. While it is marked:
- A start still on its way to the agent is withdrawn, and the job fails with Agent '…' is marked offline. The job was not sent., rather than running later.
- A Kill on a legacy job is held, with the job in Running (To Be Terminated), and is sent after you clear the mark.
- A legacy job's output, SAP lookups and z/OS JCL are refused with … is not available: agent '…' is marked offline.
- The agent's Offline and Online notifications don't fire.
Mark Offline then Clear Mark resets one agent's connection without touching the other agents on its relay. If the status shows a warning icon — Communication is not stopped. Upgrade the relay … or … Upgrade the agent … — the relay or agent is too old to stop communication: new work is still held, but upgrade it before you hand the machine to anything else. On an OpCon MFT, OpCon RPA or EASE agent, which has no connection to close, Mark Offline only holds new work. See What Mark Offline does to communication.
Marks take effect within a few seconds rather than instantly, so a job dispatched as you set one still runs. To find every agent currently marked, use the Status filter on the Agents tab — it picks any of Online, Offline, Unknown, Marked Draining and Marked Offline, matching what the status shows — or the Agents report. A machine can also set a mark itself, with a machine-status event — see Events raised by a legacy agent.
The status tooltip's Set by line says who set a mark. A mark you set from the Agents tab shows
your email. A $MACHINE:STATUS event a signed-in person sent, through a Self Service button or the
events API, shows that person's name; one a job, a workflow, a notification or the machine itself
raised shows Set by system. The Audit History report's Changed By follows the same rule — see
Taking an agent out of service.
You can also be told when someone marks an agent: agent notification groups offer Marked Offline, Marked Draining, and Mark Cleared triggers (Manage notifications).
How Workflows Pick an Agent
When a Builder designs a job, they choose a specific agent or an agent pool. A legacy LSAM job can instead target a legacy agent group. The assignment picker offers only the agents, pools and groups whose type and OS match the work; a Universal Agent pool qualifies when it holds at least one such agent, and its job still goes to whichever agent in the pool asks first. A job pinned to a specific agent (or to a group with no member online) waits rather than failing, so check the target if such a job sits waiting.
What actually happens to the job:
- Agent pool, whichever mode is chosen: the job goes on the pool's queue once, and the first Universal Agent in the pool to ask for work runs it. Nothing picks the least-busy agent, and run on all does not run the job on every agent.
- Specific Universal Agent: the job goes on the queue of that agent's pool, so any agent in the same pool can take it. If the work must run on one machine, give that agent a pool of its own.
- Backup agents (secondary, tertiary, quaternary): when a Specific Agent job's primary cannot take it, the job runs on the first backup that can. Marking an agent Offline for maintenance therefore moves jobs that name a backup onto it — see Backup agents.
- Legacy agent group: least-tasked picks an online member at random; run on all makes one job per member. For an OpCon MFT, OpCon RPA or EASE job, a member whose relay has that kind of job turned off is never picked, and neither is such a backup agent.
- Job types with one choice: a SMAFT File Transfer or OpCon RPA Task job runs on a specific agent only, with no backup agents — see Which assignments a job type allows.
A few things about how a Universal Agent runs work are worth knowing before they surprise you: every job stops at one hour, the agent doesn't take new work until the whole batch it last picked up has finished, and Kill doesn't reach it. See How a Universal Agent takes and runs work.
A legacy agent group holds one agent type, so adding an agent of any other type to it is refused — including an OpCon MFT agent to an OpCon RPA or EASE group, and any other pairing of the three. The REST-reached types are as distinct from one another as any of them is from a Windows LSAM.
Manage Legacy Agents and Groups
Legacy LSAM agents are registered on the Agents tab: select New Agent, choose the agent's
type in Choose Agent Type, then fill in its Name, Relay, host and ports. Select a legacy
agent to edit it — its type and relay can't be changed — and use its row menu to delete it.
OpCon MFT, OpCon RPA and EASE agents are registered the same way, even though
none of them is an LSAM — each is reached over its own HTTPS REST API rather than the LSAM wire, and
each needs a relay that has reported it can serve that type. Changes take effect automatically: the connecting relay picks
them up within about a heartbeat, with no restart. Give each legacy agent a name that's unique for
its relay and 128 characters or fewer — the platform accepts a longer name, but the relay won't
connect to that agent, so it never comes online. An MCP agent's name must also end with a
period and be at most 24 characters, such as MCPPROD., or the agent is refused — see
MCP agent names. A z/OS agent's name is at
most 8 characters and is saved in upper case, so zprod1 becomes ZPROD1 — see
z/OS agent names.
The ports start at the type's defaults: LSAM Port 3100 with JORS Port empty, except for
SAP R/3 and CRM, which starts at 13100 and 13110, and SAP BW, which starts at 14100
and 14110. Change them if the machine listens elsewhere; switching the type afterwards keeps a
port you typed. An SAP BW agent registered earlier on the defaults kept 13100 and 13110; if it
never connects, set the ports it really listens on. A BIS agent shows no JORS Port, because
it has no JORS listener. BIS agents can be registered and connected, but no job
type runs on them yet; an SAP R/3 and CRM agent runs the
SAP R/3 Job type, an
SAP BW agent the SAP BW Process Chain
type, a z/OS agent the six z/OS
types, an MCP agent the six MCP
types, and an OS 2200 agent the OS 2200 Job
type. Until an agent's JORS Port is set, its jobs' Output tab cannot list their output — which is where a z/OS agent starts — and a z/OS agent's JCL cannot be viewed or saved. To turn JORS off, leave JORS Port blank or enter 0; clearing it on an existing agent removes the port it held. An SAP agent's Query Listener Port must be the port the agent listens on for queries, or
the SAP lookups and Check SAP Job Numbers cannot reach it. See
Agents and agent pools.
Decide whether a legacy agent's jobs can be killed
The legacy agent form carries an Allow Kill switch for the agent types that can be killed. It decides whether an operator's Kill reaches the jobs on that agent, or is refused while the job keeps running.
- Open the agent on the Agents tab, or start a New Agent of a legacy type.
- Read the hint under Allow Kill: Platform default: on (or off) means the agent follows its type's default — on for Windows, Unix, IBM i, MCP, z/OS and SQL, off for SAP R/3 and CRM.
- Turn the switch on or off to override the default. The hint then reads Overrides the platform default (…), and Use platform default returns the agent to the default.
- Save the agent.
SAP BW, OS 2200 and BIS agents show no switch: their jobs can never be killed. OpCon MFT, OpCon RPA and EASE agents show none either, and Kill on their jobs is unchanged. See Allow Kill.
Match a legacy agent's CRC and XML escaping
Most agents never need these. Change them only when an agent's messages carry no CRC, or its job values must arrive escaped or unescaped differently from its type's default.
- Open the agent on the Agents tab, or start a New Agent of a legacy type.
- In the type's settings section, turn Check CRC off for an agent that sends no CRC. It is on by default on every legacy type, and saving a change reconnects the agent.
- On a Windows, SQL or MCP agent, set Requires XML Escape Sequences — on by default for Windows and SQL, off for MCP. It applies to jobs started after you save.
- Save the agent.
Changing either from its default needs a relay that has reported it can apply it. Behind an older relay, a changed Check CRC is refused on save, and an agent whose XML escaping differs from its default has its jobs refused at dispatch. See Check CRC and Requires XML Escape Sequences.
Set each legacy agent's default event environment
A legacy agent's New Agent and Edit Agent dialogs carry a Default event environment. It has nothing to do with where the agent's jobs run — it is the one environment that events the machine itself raises are applied to, when a job or process on it writes an event file into the agent's MSGIN directory.
Registration refuses an event-raising legacy agent with no environment — every legacy LSAM type and EASE. (An OpCon MFT or OpCon RPA agent has no MSGIN directory, so it is not asked for one.) What you enter is also checked against your tenant's environments as you save it, so a typo or a retired environment is refused on the spot rather than losing events weeks later.
You can still clear it when you edit an agent, and while it is unset every event that machine raises is refused — the machine deletes the event file before the platform sees it, so the event is lost and the refusal doesn't appear in the event log either.
It is per machine: one machine sends everything to one environment, and there is no per-event override. A machine shared across environments still needs one chosen. See Events raised by a legacy agent.
Agents registered before the field became required can still be unset. While any are, the Agents tab shows a warning that counts them across every relay, with an Assign environment… action that sets one environment on all of them at once. It fills only the agents still unset, so nothing you have already configured is overwritten. See Finding and fixing the agents that have none.
Choose the SAP events an SAP agent watches
An SAP R/3 and CRM agent can raise OpCon events when SAP events occur. To set them, complete the following steps:
- Open the agent on the Agents tab, or start a New Agent of that type.
- In SAP R/3 and CRM settings, under SAP events to monitor, select Add SAP event.
- Enter the SAP event, and a Parameter if the event carries one.
- In OpCon events, enter the events to raise, one per line, up to 20.
- Save. The change is sent to the agent at once, whether it is online or not.
An empty list stops nothing until the agent restarts: it keeps watching its previous SAP events until then. The limits and messages are in SAP events to monitor.
Record an SAP agent's system details
An SAP R/3 and CRM or SAP BW agent's settings section also holds its SAP system details — Client ID, Gateway, System Number, R3 Name, Group, RFC Trace and, on SAP R/3 and CRM, Audit Level. Enter them as they are set in the agent's own SAP configuration, and save. Saving them never reconnects the agent. The agent signs on to SAP with them to answer the SAP lookups in the job editor and Check SAP Job Numbers, so details that do not match its own SAP configuration make those fail. They are not sent with the agent's jobs, so they do not change how its jobs run. The values each takes are in SAP system details.
Choose how an OS 2200 agent's jobs start
An OS 2200 agent's OS 2200 settings section has one setting, Job Start Format. Leave it at Default (XML) for a current OS 2200 LSAM. Set it to Non-XML only for an older LSAM that cannot read XML, and save. The change applies to the next job that starts, with no reconnect.
XML needs a current relay: until every relay that serves the agent is upgraded, its OS 2200 jobs are refused with RELAY_LSAM_FEATURE_UNSUPPORTED, and Non-XML runs them in the meantime. See OS 2200 Job Start Format.
Encrypt the connection to a legacy agent
A Windows, Unix, IBM i, MCP, z/OS or OS 2200 agent can have its relay encrypt the scheduling and job-output connection to it.
- Turn TLS on in the agent's own configuration first.
- On the agent's form, turn on Use TLS for Scheduling.
- Leave TLS Server Name blank if the agent's certificate carries its LSAM Host as you entered it; otherwise enter a name the certificate does carry.
- Turn on Check Certificate Revocation only if the relay can reach the revocation service.
- Save. At its next check-in the relay reconnects the agent over TLS.
The agent comes back online. If it stays offline, the relay's log names the TLS reason.
The save is refused until the agent's relay is 1.24.0 or later. A certificate from an authority the relay's host already trusts needs nothing more; for your own authority or a client certificate, set the relay's TLS variables. JCL cannot be viewed or saved on a z/OS agent while the switch is on. See Use TLS for Scheduling and Scheduling TLS variables.
Give a legacy agent a file-transfer endpoint
A SMAFT File Transfer job connects one legacy machine directly to another, so every machine that takes part needs a file-transfer endpoint. Open the agent on the Agents tab and find the File Transfer (SMAFT) section. It appears on an existing agent only — register the machine first, then set its endpoint — and only for the types that can take part in a transfer: an SQL, SAP R/3 and CRM, SAP BW or BIS agent has no such section.
- Set FT IP Address to the address the other agent uses to reach this machine. Blank inherits the agent's LSAM host.
- Set FT Port (non-TLS) if the machine does not use the platform default — 3110 on Windows, 3108 on UNIX and the other platforms that support file transfer. SQL, SAP R/3 and CRM, SAP BW and BIS machines have no default, because they take no part in file transfers. Set FT Port (TLS) only if you intend to use TLS; there is no default for it.
- Set FT Role to decide which transfers this machine may take part in: source only, destination
only, both, or none. Blank inherits
None, so this step is not optional — a machine with no role set appears in neither picker and takes part in no transfer. - Leave the two Supports … transfers switches alone unless the machine differs from the defaults — non-TLS on, TLS off.
Leave a field blank to inherit its default. The hint under each field tells you which you are
looking at: Inherited - currently 3108 (default for this platform) or Override - stored as ….
Clearing the address, either port, or the role returns it to inheriting. The two switches cannot be
returned to inherited once toggled.
The relay reaches an agent on one address; for a transfer, the other agent reaches it directly, which is often a different route entirely. An address that works for the relay is no evidence it works for a transfer — so when a transfer fails to connect while both machines report online, check this field first.
No role was backfilled onto agents that were registered before the file-transfer endpoint existed, so each of them inherits None and takes part in nothing until you set a role. A job that already names such a machine still saves, then fails at dispatch naming the machine and the role to set.
If a machine is missing from a transfer's Source Machine or Destination Machine list, check its role before anything else.
For the full field reference, the defaults, and what a role of None excludes, see File-transfer endpoint.
On the Agent Pools tab you can gather legacy agents into a legacy agent group: create a pool with a legacy Type, or pick groups in a legacy agent's Agent Pools field. Every member of a group must be the same legacy type (for example, all UNIX), and a group can span more than one relay. A Builder can then point a legacy job at the group instead of a single machine, to run on one online member (picked at random, not by load) or on every member at once. A group can be deleted once it has no members; deleting it leaves the agents that were in it untouched.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| A job is waiting on a machine | No matching agent is online (wrong type/OS, or all offline/draining). A job pinned to a specific agent waits for that agent, or for one of its backup agents if it names any; it also waits while the agent can't be found or its status can't be checked, and while a legacy agent's relay hasn't reported it for more than five minutes. A Universal Agent pool job waits while the pool has agents and none of them is online and unmarked. The job's Status History has an Agent Availability Hold entry that says why. | Bring a matching agent online; check the job's required agent type, or reassign the job. |
| An agent shows offline / stale heartbeat | The agent host or its connection is down | Check the agent machine and network. |
| A legacy agent shows Unknown (yellow) | Its relay can't be reached, or the relay reports it can't tell whether the agent is reachable, so the agent's state is uncertain, not necessarily down | Check the relay; the agent leaves Unknown on its own once the relay reconnects. If the relay stays gone for an hour, the agent reads Offline instead. |
| A legacy job targeting a group waits | The group has no member the platform can dispatch to, and the job holds rather than failing: no members yet, every member Offline, members all Unknown because the relay was lost, an online member whose relay dispatch pool hasn't resolved, every usable member marked, or every usable member on a relay that hasn't reported it can run the job's platform | Bring a group member online, add one, clear a mark, check the relay if members show Unknown, or upgrade the relay. |
| A legacy job fails to initialize with LSAM_AGENT_TYPE_MISMATCH: this job needs an agent of type … | The job's machine name points at an agent of another type — for example after the agent was deleted and re-created under the same name as a different type | Have the Builder point the job at an agent of the type the message names, or re-register the agent as the right type. See A legacy job aimed at an agent of another type. |
| A legacy job targeting a group fails to initialize | It was force-started onto a group with no member online, or the last usable member dropped just as the job was released | Bring a member online, then restart or re-add the job. |
| An agent looks healthy but takes no work | It's marked. A mark survives a reconnect, so one set during earlier maintenance is still in force. | Hover the status for the reason, then Clear Mark. |
| A Marked Offline agent shows a warning icon, Communication is not stopped | Its relay, or the Universal Agent itself, is too old to stop communication; new work is still held | Upgrade the relay or the agent. See What Mark Offline does to communication. |
| Work piles up on one agent | Its concurrency cap is reached — on a Universal Agent, its own MAX_CONCURRENT_JOBS setting | Raise MAX_CONCURRENT_JOBS on the agent machine and restart the agent, or add agents to the pool. |
| A new Universal Agent never comes online | It was installed with the commands New Agent shows for Universal, which don't register it | Register it through the API and give it its credentials file — see Registering a Universal Agent. |
| An operator's 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 | Turn Allow Kill on for the agent if its jobs should be killable. See Allow Kill. |
| A legacy agent with Use TLS for Scheduling on stays offline | The relay cannot complete a TLS connection: the agent's TLS is off, its certificate does not carry the expected name, or it does not chain to an authority the relay trusts | Read the relay's LSAM connection failed: TLS: … log line and fix what it names. See Scheduling TLS variables. |
| A pool's Delete is disabled | The pool still has agents | Remove or delete its agents in Edit Agent Pool, then delete it. |
| A Universal Agent moved to another pool still runs the old pool's work | The move takes effect at the agent's next sign-in refresh | Wait up to about 15 minutes, or restart the agent. |
| A job for one Universal Agent ran on another | It went on the queue of that agent's pool, and another agent in the pool took it | Give the agent a pool of its own. |
| A tab is missing, or an action is unavailable with You do not have permission to … | Your roles do not grant that permission under All workspaces | Grant the Agents, Agent Pools or Relays permission under All workspaces — see Agents, agent pools and relays are checked. |
A Universal Agent's Edit Agent dialog doesn't display its CPU, memory, disk or installed
plugins, so they read -- whatever the agent reports. That is expected, not a fault on the agent.
Related topics
- Agents and agent pools — full configuration reference and troubleshooting
- Prepare agents for connectors (Administrator)
- Manage plugins (Administrator)