Enabling agents, functions, and API workflows

Set up UiPath Robot 2026.10 to run agents, functions, and API workflows on your machines, with Agent slots, Function slots, and the Local runtime type.

A Robot 2026.10 on Windows runs agents, functions, and API workflows next to RPA processes, on the same machine and the same connection to Orchestrator. This works with Orchestrator in Automation Cloud and Automation Suite. Orchestrator sends these jobs to your machine when the job's runtime type is Local, and the machine template has slots for them.

はじめる前に

• An unattended robot on Windows, running UiPath Robot 2026.10 or later. For setup, refer to Installing the Robot.
• The robot connected to Orchestrator with client credentials. Robots connected with a machine key don't run agents, functions, or API workflows by default. Refer to Connecting the Robot to Orchestrator.
• Units available in the tenant for agents, which consume units for each run. Functions and API workflows run on an unattended runtime or on units.

The robot needs no other setting. The executor packages ship with the Robot, and the robot reports agents, functions, and API workflows to Orchestrator as soon as it connects, before it runs any of these jobs. The language runtimes the executor packages need, such as Python, are not part of the installation: the executors download them the first time they run a job, so the machine needs outbound internet access for that first job. For machines without internet access, refer to Executor packages > Offline machines.

Set Agent slots and Function slots

1. In Orchestrator, open the machine template your robot connects with.
2. In Agents and Functions runtimes, set:
   • Agent slots: how many agent jobs run at the same time on each connected machine.
   • Function slots: how many function and API workflow jobs run at the same time on each connected machine.
3. Save the machine template.

Both values default to 0, so a machine runs none of these jobs until you raise them. Slots don't consume licenses. They reserve capacity on the machine itself.

To run functions and API workflows on your Unattended licenses instead of units, select Use Production (Unattended) under Function slots. These jobs then run on the Production (Unattended) runtime type and share the template's Unattended runtimes with RPA jobs.

For the full steps, refer to Adding a Machine Template in Automation Cloud or Automation Suite.

Run a job on your robot

1. Start a job for an agent, function, or API workflow process.
2. In Runtime type, select Local for an agent, or Local - Function for a function or API workflow. If the machine template uses Use Production (Unattended), select Production (Unattended).

Orchestrator sends the job to a connected robot that reports the process type. If no capable robot is connected, the job waits as Pending until one connects.

To check that the job ran on your machine:

• In Orchestrator, the job's details show the machine that ran it, and the job's logs come from that robot, as for an RPA job.
• On the machine, the Robot log, Robot.log, has entries that start with [ExecutorsHost] for the host process that ran the job. In service mode, the log is in %ProgramData%\UiPath\Logs\internal. In user mode, it's in %LocalAppData%\UiPath\Logs\internal.

For how the Local runtime type and its capacity pools work, refer to Agents and Functions on Local Robots in Automation Cloud or Automation Suite.