Orchestrator release notes

Added April 28, 2026: This feature was released on April 27, 2026, but was not included in the release notes at the time.

We enhanced the Tenant – Overview and Folder – Home pages with a new Latest jobs to help you quickly monitor recent job activity.

From the Latest jobs card, you can quickly:

This enhancement provides better visibility into job activity directly from both the Tenant and folder home pages.

You can now filter jobs across folders, making it easier to monitor and analyze executions at scale.

This new capability is available in Tenant → Monitoring → Jobs and allows you to quickly find relevant jobs across multiple folders using advanced filtering options.

Cross-folder filtering is currently available only at the tenant level. When accessing the Jobs page from a specific folder, results are limited to that folder and do not include jobs from its subfolders.

For more information, check the Jobs page from the Monitoring section in the Orchestrator user guide.

Added May 4, 2026: This feature was released on April 27, 2026, but was not included in the release notes at the time.

Job status values and Jobs history chart segments on the cross-folder Tenant page are no longer just informational. You can now select any job status to open the Jobs list with the corresponding status filter already applied.

This makes it easier to quickly access running, pending, or failed jobs without manually applying filters.

The Job details side panel now displays a warning when a job is started using input arguments sent as attachments due to input size restrictions. The message provides guidance on resolving compatibility issues with robot versions.

For more information, check the About input and output arguments.

The Job Details side panel now includes a new Compatibility field within the Execution Environment section.

This addition provides clearer insight into the environment compatibility of each job, helping you better understand how and where jobs are executed.

You can now add static IPs to the allowlist for Automation Cloud Robots - Serverless and not open your network to all external IPs in Canada, Singapore, and UAE regions. To use static IPs, you must explicitly enable this option in your serverless robot template. After enabling them, you can add the corresponding IPs to your allowlist. For the list of static IPs, check the Static IP configuration page from the Automation Cloud admin guide.

The release of the Orchestrator Credentials Proxy 2.2.1 brings the following updates:

For details, check out the Orchestrator Credentials Proxy documentation.

We are excited to introduce the Automation Registry, a centralized, cross-folder experience for discovering, managing, and governing automations, and related resources across your environment. It provides visibility across all available automation types in UiPath, including RPA workflows, API automations, and agents. The Registry page provides a unified view across three key areas:

For more information, check the About the Registry context page.

A new Duplicate job action is now available for jobs. This option opens the Start Job form pre-filled with the original job’s configuration. The Duplicate job action replaces the Restart job action and enables the option for any state. Previously non-terminal states (Pending, Running, Stopping, Terminating, Suspended, Resumed) could not have been acted upon.

The webhook URL is now available on the Package Requirement page for event triggers, making it easier to access when needed.

We included a hint for the disabled VM option in the Unattended setup page to explain that VM configurations are not supported. The hint also includes a link to the relevant documentation. This is available for both UiPath-hosted and self-hosted unattended robots.

Queue triggers can now continue processing new queue items even when previously started jobs are in a Suspended state. This ensures that remaining items in the queue are picked up without requiring additional item uploads or manual intervention.

We introduced a Reset to default button for runtime arguments. This option lets you easily restore any field to its package or process default value. When restarting a job, this action resets values to their configured defaults, not to the values from the previous run.

We fixed an issue where personal workspace sub-folders were returned by the /odata/Folders API.

We fixed an issue where upgrade or rollback operations could fail with Error code - 1001, Message - "The name is already used" due to resources being recreated with the same name.