Unified Runtime

Unified Runtime, the single runtime in UiPath Robot 2026.10 that runs every workload through the .NET executor and executor packages.

Unified Runtime is the runtime in UiPath Robot that runs every workload: RPA processes, test cases, agents, functions, and API workflows. It hands each job Orchestrator sends to the executor that workload needs, so one install, one machine template, and one connection to Orchestrator cover all of your automation on a machine.

Executors

Unified Runtime runs each workload in an executor, the component built for that kind of work:

• The .NET executor runs RPA processes and test cases, for Windows, Windows - Legacy, and cross-platform projects. For how it runs on the machine, refer to Robot Executor.
• Executor packages run agents, functions, and API workflows. The Python executor runs agents and Python functions, and the JavaScript executor runs JavaScript functions and API workflows. They ship with the Robot and update with it. For details, refer to Executor packages.

Low-code agents and coded agents share one executor path. An agent built in Agent Builder and an agent written in Python run the same way, at design time and in production.

What the robot tells Orchestrator

When a robot connects, it reports which process types it can run. RPA processes and test cases are always on that list. Agents, functions, and API workflows are on it when the matching executor packages are available on that machine. Orchestrator only sends a job to a robot that reports its process type. A robot connected with a machine key doesn't run agents, functions, or API workflows by default. If none is connected, an agent, function, or API workflow job waits as Pending until one connects.

Where it runs

Agents, functions, and API workflows need UiPath Robot 2026.10 (LTS). On that version, they run on unattended robots on Windows, and are generally available. Support for Linux is planned.

How it uses capacity

Unified Runtime draws on two kinds of capacity, set side by side on the machine template:

• Runtimes cover RPA processes and test cases. One runtime lets one job run at a time on the machine.
• Agent slots and Function slots cover agents, functions and API workflows. One slot lets one job of that type run at a time on each connected machine. Both default to 0, so a machine runs none of these jobs until you raise them. Functions and API workflows use Production (Unattended) runtimes instead when Use Production (Unattended) is selected on the machine template.

For the full job lifecycle, refer to How a job runs.

How it is paid for

The workload decides what a job consumes, not the runtime. RPA processes and test cases use runtimes or user licenses. Agents, low-code and coded, consume units, Platform Units in Unified Pricing or Agent Units in Flex. Functions and API workflows run on an unattended runtime you already have, or on units. Agent slots and Function slots don't consume a license. Consumption doesn't depend on machine size, because the machine is yours.

For details, refer to Licensing the Robot.

What it sends back

Unified Runtime reports each job's status, logs, and traces to Orchestrator. Agent traces include the prompts and responses of each model call, whichever model the agent calls. For what leaves the machine and how to limit it, refer to Tracing and data controls.