Orchestrator release notes

DELIVERY:

Last updated Oct 27, 2025

2023.10.4

Release date: April 3, 2024

Bug fixes

Erratum - added December 15, 2024: We previously addressed an issue in an erratum dated July 3, 2024, concerning the inability to save custom configurations in the email settings due to a form validation issue. The specific issue was that the Save button appeared greyed out, even when all required fields in the form were correctly filled in. This was said to be fixed, enabling users to successfully submit the form once all necessary fields have been meticulously filled in. However, upon further review, we regret to inform you that this issue has not been completely resolved. We apologize for any confusion or inconvenience caused and want to assure you that we are actively working towards a definitive solution. Find a workaround in the known issues section.
The performance of fetching items from folders with large numbers of assets has been improved.
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.
For versions 2023.4 and up, identity/.well-known/openid-configuration is unable to load due to <add name="X-Content-Type-Options" value="nosniff" />. Therefore, you must remove it from the Identity appsettings.Production.json file.
This release brings security updates and patches to address Common Vulnerabilities and Exposures (CVEs).
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)".

Known issue

Issue with saving custom configurations in email settings

Erratum - added December 15, 2024: When configuring the email settings, you cannot save any custom configurations due to an issue with form validation. The Save button incorrectly appears grayed out, despite filling in all the required fields correctly. As a workaround, you can make a PUT request to the /identity_/api/setting endpoint.

Use the appropriate access token and make sure the request body contains the necessary details. Also make sure that Email.Smtp.UseDefaultCredentials is set to True, like in the following example:

{
    "Settings": [
        {
            "Key": "Email.Smtp.Host",
            "Value": "SendGrid"
        },
        {
            "Key": "Email.Smtp.Port",
            "Value": "587"
        },
        {
            "Key": "Email.Smtp.UserName",
            "Value": ""
        },
        {
            "Key": "Email.Smtp.Domain",
            "Value": ""
        },
        {
            "Key": "Email.Smtp.FromEmail",
            "Value": "[email protected]"
        },
        {
            "Key": "Email.Smtp.FromDisplayName",
            "Value": "UiPath Platform"
        },
        {
            "Key": "Email.Smtp.EnableSsl",
            "Value": "true"
        },
        {
            "Key": "Email.Smtp.UseDefaultCredentials",
            "Value": "true"
        },
        {
            "Key": "Email.Smtp.Password",
            "Value": ""
        },
        {
            "Key": "Email.Smtp.ConnectionTimeout",
            "Value": "180000"
        }
    ],
    "PartitionGlobalId": ""
}{
    "Settings": [
        {
            "Key": "Email.Smtp.Host",
            "Value": "SendGrid"
        },
        {
            "Key": "Email.Smtp.Port",
            "Value": "587"
        },
        {
            "Key": "Email.Smtp.UserName",
            "Value": ""
        },
        {
            "Key": "Email.Smtp.Domain",
            "Value": ""
        },
        {
            "Key": "Email.Smtp.FromEmail",
            "Value": "[email protected]"
        },
        {
            "Key": "Email.Smtp.FromDisplayName",
            "Value": "UiPath Platform"
        },
        {
            "Key": "Email.Smtp.EnableSsl",
            "Value": "true"
        },
        {
            "Key": "Email.Smtp.UseDefaultCredentials",
            "Value": "true"
        },
        {
            "Key": "Email.Smtp.Password",
            "Value": ""
        },
        {
            "Key": "Email.Smtp.ConnectionTimeout",
            "Value": "180000"
        }
    ],
    "PartitionGlobalId": ""
}

Error while trying to run the `MigrateTo-ResourceCatalog.ps1` script

Erratum - added April 17, 2024

The following error can sometimes occur while trying to run the MigrateTo-ResourceCatalog.ps1 script: This command cannot be run due to the error: The system cannot find the file specified. This only happens when the start process command tries to execute a file that cannot be located.

To overcome this issue, we recommend adding the following line to the Init-TempFolder command within the script:

$script:cliPath = Join-Path $script:cliPath "\UiPath.ResourceCatalogService.CLI.exe"$script:cliPath = Join-Path $script:cliPath "\UiPath.ResourceCatalogService.CLI.exe"