orchestrator
2020.10
false

OUT OF SUPPORT
Orchestrator Release Notes
Last updated Dec 12, 2023
2020.10.6
linkRelease date: 24 February 2021
Improvements
link- You can now enable NuGet package caching via the
UiPathOrchestrator.dll.config
file to improve performance in large-scale environments. - You can now upload NuGet packages targeting
net5.0
TFM. - Previously, retrieving credentials from a CyberArk vault did not work when using Path authentication, and a
Script run using untrusted shell.
exception was thrown. As of now, you can enable thePlugins.SecureStores.CyberArk.UsePowerShellCLI
app setting to overcome this issue. - Adjusting the flush interval and size for the SubmitLogs endpoint is now possible using two new configurable
UiPath.Orchestrator.dll.config
settings:RobotsLogs.Flush.Interval
andRobotsLogs.Flush.BatchSize
.
Bug Fixes
link- A high rate of lock contentions was identified during application execution, causing performance issues. We reduced lock contention to improve performance and scalability.
- We addressed a performance issue that occurred due to the SQL Server CPU reaching full capacity when connecting more than 100k robots.
- You could not log out of Orchestrator in Internet Explorer after adding Orchestrator to IE’s Compatibility View list.
- New Relic APM for ASP.NET Core was causing startup errors due to the
PublishTrimmed
flag being used by Identity Server. This behavior no longer occurs. - Trying to encrypt the
UiPath.Orchestrator.dll.config
file'snlog
section would result in an error. This behavior is no longer present. - Triggering two jobs simultaneously in a classic folder resulted in one of them not being executed unless launching it manually a second time. Such jobs are now picked up by the Robot and properly executed.
- Some default activities packages had either missing dependencies or dependencies with the wrong version.
Known Issues
linkAdded March 4, 2021
Alerts and webhooks are not triggered when the robot status becomes unresponsive. If you rely on this feature, please be aware of this issue when upgrading to 2020.10.6 or 2020.10.7 Orchestrator. This issue will be fixed in 2020.10.8.