Orchestrator release notes

We improved accessibility across several user interface components to support better usability.

When starting a job, the first available process in the list is now automatically selected based on name ordering.

This change streamlines the job start flow and reduces the number of steps required when launching jobs.

Starting a job using Run Agent now returns a clearer error message when the required Robot permissions are missing.

The error message now clearly indicates when the failure is caused by missing permissions to start a job, helping you identify and resolve configuration issues more quickly.

You can now delete video recordings directly from the More Actions context menu.

Previously, the Delete recording option was only available in Job Details, which made it harder to discover. This update improves usability by making the action easier to access.

OData APIs now include additional information in error responses when a request contains invalid or malformed query parameters.

You can now remove per-user and per-robot asset values more safely and efficiently when editing an asset.

When removing a value, a confirmation dialog is displayed to help prevent accidental deletions. The dialog displays the name of the user or robot whose value is about to be removed.

You can also select multiple values and remove them at once using the Remove button in the asset values grid.

Both columns are hidden by default and can be enabled through the column visibility settings, allowing you to view when a transaction item was created in either relative or exact timestamp format.

Deleting roles in Manage Access → Roles now includes an improved confirmation modal.

When deleting a role, you must type the role name to confirm the action. This helps prevent accidental deletions and provides clearer guidance about the impact of removing a role, including the effect on users who currently have the role assigned.

This event helps you monitor retry activity and react to queue items that are automatically or manually retried after a failure.

You can now remove per-user and per-robot asset values more safely and efficiently in the Assets editor.

When you delete a value, a confirmation dialog is displayed that includes the name of the affected user or robot, helping prevent accidental deletions.

You can also select multiple values and remove them at once. The grid now supports multi-selection, and when you choose Remove selected, the system displays a confirmation dialog describing how many entries will be removed.

We’re excited to announce that Integration Service connections have moved to Orchestrator.

This enhancement centralizes the management of your connections, making it easier to configure, monitor, and secure connections.

As we previously announced in Rollout of new audit log retention policies, we are now entering the next phase of this change.

Now that the audit log retention policies have been fully rolled out, we will begin removing audit logs from the Orchestrator database that are older than the six-month retention period.

Audit log archives are available for the 18 months that precede the most recent six-month window. For Enterprise plans, archives cover the preceding 18 months, ensuring that audit log data is available for at least 24 months in total. For Community plans, archived data is available for up to 6 months.

Automatic deletion of archives older than 24 months will be implemented in a future update.

For additional information, refer to Downloading archived data.

Check the following table for the scheduled dates by region (subject to change).

Automation Cloud Robots - VM is now available in the United Arab Emirates region. This ensures your data is securely stored and replicated across multiple availability zones within UAE, offering full control and compliance confidence.

MCP Servers are now available in the United Arab Emirates region.

This expansion ensures that data processed through MCP Servers is stored and replicated within UAE's availability zones, supporting regional data residency and compliance requirements.

To learn more about the available tenant regions and the services offered in each region, explore our resources on Data residency.

For more information on MCP Servers, check the MCP Servers section in the Orchestrator user guide.

We recently rolled out a new feature that allows you to self-manage Robot version updates for Automation Cloud Robots-VM and Elastic Robot Orchestration pools based on custom images.

Robot version updates begin on March 9 for pools with UiPath-managed updates enabled, depending on the configured instant or delayed auto-update preference.

We improved how webhook names are displayed. Previously, HTML content included in a webhook name could be rendered as formatted content in confirmation dialogs.

Webhook names are now displayed strictly as plain text, preventing unintended HTML rendering and improving overall security.

This update provides more granular access control while maintaining backward compatibility.

The folder sidepanel now automatically collapses on smaller screen resolutions to improve usability and optimize available workspace.

We’ve enhanced the folder-level access rule configuration by adding search capabilities to the Credential Stores selection list when configuring access rules.

Previously, when editing access rules at the folder level, credential stores were displayed in a scrollable list without a search option.

You can now use the search box to quickly find and select the desired credential store, improving usability and configuration efficiency.

After this period:

This change improves scope granularity and aligns access control with the principle of least privilege.