2021.10.2

Release date: 2 February 2022

What's New

Note: The UiPathOrchestrator.msi installer now works with ASP.NET Hosting Bundle 6.0.x.

Orchestrator 2021.10.1 shipped with a new mechanism for launching jobs via queue triggers. The behavior was enabled by default and could not be disabled. Due to being deemed unsuitable by some of you, we decided to revert to the previous way in which Orchestrator accounted for only new queue items when computing the number of target jobs that must be reached.

Bug Fixes

• Orchestrator did not release the attended license of an inactive user when their personal workspace was converted to a folder.
• The default SignalR setting in Orchestrator (with only the Websocket transport selected) prevented the corresponding remote robot utility UiPath.RemoteDebugging.Agent.exe from executing in multi-node environments (either standalone or Automation Suite installations).
• Orchestrator threw the following exception when both the zh-CN and zh-Hans locales were installed on its machine: TimeZoneService Class Instantiation throws System.ArgumentException: An item with the same key has already been added. Key: zh-CN due to available locales
• Upon upgrading to 2021.10.1, Orchestrator failed to send email alerts when the Use default credentials option was enabled. Email alerts are now successfully sent.
• Occasionally, test set and test schedule executions failed with the following error:

  System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.PlatformNotSupportedException: This platform does not support distributed transactions.

  Test sets and test schedules are now executed with no errors.

• We corrected an issue where enabling the Use default credentials option cleared the SMTP Username field, but did not clear the SMTP Password field.
• Orchestrator installation would fail when using ASP.NET Core Module 5.0.3 and newer.
• AD users could not log into Orchestrator from a Turkish browser when the domain name had the letter i due to a localization issue.
• Users who did not have the Tenant Administrator role and tried to access the Identity Management portal saw a blank page. Now the “URL is not valid” screen is displayed instead, with options to go to the profile page or sign in page.
• When setting up system email notifications, enabling Use default credentials failed to reset the user-defined SMTP password.