Orchestrator release notes

DELIVERY:

Last updated Apr 22, 2025

2024.10

Release date: October 21, 2024

Administration improvements

Exception details

Exception details are now displayed in the MSI log if the SQL validator encounters errors during application upgrade.

New parameter to control webhook validation

We have added a new parameter, Webhooks.VerifyAvailability.Enabled, to the UiPath.Orchestrator.dll.config file, with a true or false value. Set the parameter to false to disable webhook reachability validation when configuring the webhook target in the user interface.

Removing SQL Server 2014 support

SQL Server 2014 is no longer supported. Please use SQL Server 2016+ instead.

Update service changes

Erratum - Added February 5, 2025

We have changed the behavior around initiating updates during job execution. As such, the Robots application no longer forces an update to a new version if a job is still running. Furthermore, during an update, active Robots enter a maintenance mode, ensuring they do not take on any new jobs until the update is complete.

This change also means that the 10-minute wait time for service-mode Robots is no longer applicable.

Exporting usage data

Added April 22, 2025

You can now export a high-level usage summary from your Orchestrator environment, including metrics on robots, jobs, processes, queue items, users, and more.

Additionally, you can upload the exported data file to the UiPath® Customer Portal, to help us achieve a better understanding of usage and provide you with better support.

For details, refer to Exporting usage data.

Bug fixes

The Path column in the UiPath.dbo.OrganizationUnits database table is updated based on the Code column. If the Code column contained incorrect or stale values for deleted child folders, the installer updated them as NULL, which violated the validation requirement at upgrade time. This mainly occurred when child folders were deleted, and their parent folders were subsequently moved. This was solved by updating the Path column based on the Key column in these scenarios, such that NULL is no longer returned.
The elevate permission check no longer includes permissions coming from disabled services. Thus, the following error no longer occurs when you attempt to assign permissions to other users: "Action forbidden: You selected at least one role that grants more than your set of permissions. Please remove the following role(s): {role_name} to continue. (#1437)".
When the user interface access was disabled and a user tried to sign in, Orchestrator displayed a misleading error that the user was not authenticated.
The screen reader version of the Create new menu included items that were greyed out in the user interface. Now, if a menu item is not available for any reason, the screen reader also skips it.
Timeouts occurred when a large number of configured robots retrieved CyberArk® credentials.
When configuring the CyberArk credential store, the CyberArk Folder field did not support separators, the / or \ characters.
As a result of the My profile page removal, the Orchestrator version was no longer visible in the user interface. You can now find the version at the bottom of the user profile section.
API calls attempting to edit the details of unattended robots failed due to an unauthorized error. However, manual edits made through the user interface by the same user with identical permissions were successful.
The Process filter on the Logs page did not include the process names of automations that were run in Studio.
Assets could not be retrieved from the HashiCorp Vault, which resulted in a permission denied error.
The time format in grid exports was not always consistent. Now, it is displayed as yyyy-mm-dd hh:mm:ss.fff in all scenarios.
An error was displayed in the View transactions window when you attempted to export queue items, and had filtered for a specific robot.
In an effort to improve the readability of the queue items side panel, we have changed its layout to a row format, and have made several minor font tweaks. These updates aim to solve a rendering issue which caused content to have too little space in the old side by side layout to accommodate values. The underlying issue stemmed from a rendering change meant to account for any whitespace formatting coming from automations or raw content.
When an administrator tried to edit another administrator, it triggered an error that the authentication token was invalid, which logged out the initial user.
The Orchestrator session timed out after 30 minutes.

Common Vulnerabilities and Exposures

This release brings security updates and patches to address Common Vulnerabilities and Exposures (CVEs).

Known issues

For video recordings, Orchestrator overrides any custom retention value that you set with the default values for your license.
When you upgrade to a major version, the upgrade might fail with an error that the NLog extension UiPath.Orchestrator.Logs.Elasticsearch.dll is not compatible with the new version of Orchestrator. To avoid this issue, you should always use the latest version.
On the Monitoring page, under the Unattended sessions and User Sessions tabs, you cannot sort items by status. Alternatively, we recommend using the Status filter instead.
Local users part of local and mail-enabled AD/AAD groups may receive duplicate emails for alerts that have been generated for both groups.
SAML users cannot sign into Orchestrator if they are assigned to the Administrators group by a provisioning rule, and if their Allow Orchestrator UI Access setting is disabled. This issue occurs because the disabled user interface access setting overrides the group setting.