UiPath Release Notes

UiPath Release Notes

Release date: 24th April 2019

What's New


This new release addresses one of the most highly requested features and gives you real-time metrics to help you keep an eye on the health and state of your system. Be it in regards to Robots, Queues or Jobs, Orchestrator now provides you with a monitoring solution to ease keeping track of your deployment regardless of its size. Check it out here.

Extensibility and Performance

For an enhanced all-around sync of activities and packages in multi-node environments, package metadata is now saved to your SQL database. On top of that, instead of the ordinary File System, you can set up your Orchestrator instance to store all these artifacts in one of the following blob storage solutions: Azure, Amazon, or Minio. More information on how you can set this up is available here. Lastly, rest assured - all setup artifacts can help you easily set this up, be it for a clean installation or an update.


To further enhance the security of the Robot - Orchestrator communication protocol we added the possibility for the Robot to authenticate through a custom HTTP header. In this regard the web.config parameter, Scalability.SignalR.AuthenticationEnabled, is now at your disposal. Please note that if you enable this feature, also referred to as Robot SignalR authentication, you are no longer able to execute jobs on Robots with a version lower than 2018.4.3. More information is available on this page.

Bringing an even better segregation of sensitive information and an enhanced level of security between tenants, you can now use a unique encryption key per tenant, using Microsoft Azure's Key Vault. This has been made possible by adding a few more parameters to the already-popular web.config file. You can view more information on how you can configure these settings on this page.

In Orchestrator v2018.3 we introduced libraries to help you share reusable components at application level. In this release, we've turned our attention to segregating libraries at tenant level to ensure a more secure approach to your data. This means that in addition to the shared host feed, you may configure your libraries to use their own tenant feed.

Last but not least, the system administrator is now able to upload a library which gets propagated to all tenants which use the host feed. How cool is that? If you're interested in reading more about this feature and how to use it explicitly, visit our documentation.


If you always wondered what your Unattended Robot is up to and what exactly is going on with your unsuccessful jobs, you came to the right place. This release ships with a recording functionality that helps you troubleshoot faulted jobs. Simply configure your processes to allow recording and, whenever the corresponding jobs fail, the media files illustrating the last moments of a job are at your disposal. Keep in mind that this functionality comes with a new permissions set. Click here for more information.

Orchestrator Mobile Apps

This month the Orchestrator Mobile app also received a pretty important update that you might want to check out - you can now start jobs directly from your Android or iOS device. Other improvements have also been made available, about which you can read here.


If you regularly need to add items into your Orchestrator queues, you'll be pleased to know that we've come up with a feature which allows you to add queue items directly from a CSV or Excel file. Check it out here.

To enable you to add multiple queue items at the same time from the Orchestrator API, we added a new endpoint - UiPathODataSvc.BulkAddQueueItems. Two different upload strategies, ProcessAllIndependently and AllOrNothing, help you keep control. If you want to see an example of such a request, please see this page.

Orchestrator ships with multiple improvements regarding permissions, thus making role management easier than ever. You are no longer required to select permissions one by one. With the click of a button, you can now select each set that interests you either by category or by permission type, in case that serves you better. In addition to that, the Libraries page now has its very own set of permissions, separate from packages. Details here and here.

Furthermore, we look after power-users as well, as we provide a new web.config parameter which gives you the utmost control over roles and allows you to disable permissions from both the user interface and API. Click here for more details.

Performing GET calls to the /api/Status/VerifyHostAvailibility endpoint now requires authentication.

As you might have noticed, we've always tried to help as many people as possible to learn how to use UiPath Platform. As another piece of the democratization puzzle, we are happy to announce that, in terms of accessibility in Orchestrator, we now have achieved a Level A conformance.

To aid you in efficiently managing the manual upload of automation packages through the user interface, Orchestrator now enables you to select and transfer multiple archives at a time.

Several enhancements have been made to the /odata/Tenants endpoint. The DisplayName and Key properties have been exposed to help you pin-point your tenants in an easier fashion, with just a simple GET call. Secondly, you can now perform PATCH requests at the /odata/Tenants(Id) endpoint, to modify the DisplayName and AcceptedDomainsList properties.

It is now possible to perform PATCH requests on the /odata/Robots(Id) endpoint, so that you can easily change certain details about a specific Robot without needing to know its password and username.

Stacktrace information is no longer displayed in responses when making invalid requests to the Orchestrator API.

Package version management is now a breeze with our new bulk update feature. Yes, you heard that right. As of now you can update multiple processes at once in Orchestrator and it only takes a minute. Click here for more information.

Worried you won't be notified in time that your license is about to expire? On the contrary, you consider email alerts to be a nightmare? We've got you all covered as we added a new parameter in the web.config file which allows you to set your preferred checkpoints in terms of license expiry notification emails. By default, the parameter is configured such that emails are sent 180, 90, 30, 14, 7 and 1 day before the expiry date. See here how to configure your own values.

We know it can take a little bit for your system to get back on track after an upgrade, so in order to prevent unnecessary alerts and updates, we made it possible for you to delay the first check on your Robots' status. Add the NotRespondingRobotsJobStartDelay parameter in web.config and configure exactly for how long you want to delay the check on your robots. Details here.

Our dev team has been really preoccupied with improving Orchestrator's capabilities in this release. The overall performance has been improved a great deal, especially in highly dynamic environments. Apart from that, we took care of some specific areas as well, to give you the best experience ever. See for yourself what we handled specifically:

  • To make sure there are no performance penalties in terms of license removal, we made a few changes here and there and improved the mechanism to run smoothly.
  • We've identified an issue that was slowing down the startup performance of Orchestrator so we made sure to optimize it even in the context of complex environments with large numbers of users.
  • We were on a mission to optimize Redis cache usage and we did it. We made a series of improvements, all aimed at reducing the number of Redis calls.
  • Alert distribution has been optimized, thus ensuring a faster performing alert mechanism even in the context of many subscribers.

Coinciding with this release, there are some new additions to Orchestrator's logging solution. As of now, you may connect to databases that support the MongoDB wire protocol using the same NLog target. This means that Orchestrator Robot logs can be stored and viewed using the Cosmos DB service as well. See here details about the logging configuration in Orchestrator.

The sessionState mode parameter is deprecated and as of now defaults to Off in clean installs.

Orchestrator drop-downs have been upgraded. We now have scroll bars to help you browse through all existing entries. Happy scrolling!

The Value field for both global and per-robot text assets now allows for up to 1.000.000 characters.

To ease the management of large deployments, the Robots page can now be filtered by an environment with just a click.

The Webhooks page can now be filtered according to a webhooks' state - enabled or disabled.


In our quest for continuous improvement, we collect usage and performance data to help diagnose problems and enhance our products. This feature now also comes with the possibility of turning off telemetry at install-time through the TELEMETRY_ENABLED command line parameter or later on using the dedicated configuration keys. More information is available here for UiPathOrchestrator.msi.

As security has always been one of our biggest concerns, we have now added an extra layer. You can specify the tenant and host admin passwords directly when you install your Orchestrator instance, from the command line or the setup wizard of the UiPathOrchestrator.msi installer. If you want to find out more on this topic, access this page or this page.

To aid you in silently updating your Orchestrator instance and using the previous database, the APP_ENCRYPTION_KEY parameter of the UiPathOrchestrator.msi installer has been enhanced. More details are available in the guide.

To ensure an even better integration between Azure and Orchestrator, it is now possible to include the local activity feed in your Azure environment directly at install-time, using the newly added activitiesPackagePath parameter. To support this feature, you should also know that we added an archive, UiPathActivities.zip, with all the activities in UiPathOrchestrator.zip. To view more information on how to use this parameter, see this page.

Furthermore, to help you control where to store Robot logs in Azure deployments, a new parameter, -robotsElasticSearchTargets, had been added to the Publish-Orchestrator.ps1 artifact. More information is available here.

UiPathPlatformInstaller.exe now also verifies if you have IIS 7.5+ and URL Rewrite installed on the machine, enabling a smooth set up process.

Breaking Changes

  • The Username parameter is now mandatory for PUT requests on the /odata/Robots(Id) endpoint.

Known Issues

  • The per tenant encryption key feature can only be used in clean installations.
  • In Orchestrator installations of v2019 FastTrack that use an existing database, although you provide the admin passwords at host and default tenant level, they are not taken into account.
  • The hostAdminPassword and defaultTenantAdminPassword parameters of the Publish-Orchestrator.ps1 script do not properly enforce password complexity rules.
  • You cannot disable telemetry at deployment-time using the Publish-Orchestrator.ps1 script. However, please note that you can manually set it up as explained here.
  • Default activities cannot be uploaded by the Publish-Orchestrator.ps1 script when installing or updating your Orchestrator instance if the NuGet.Repository.Type is set to Composite.
  • If you have invalid cron schedules and you upgrade your Orchestrator instance from v2018.1.x or v2018.2.x to either v2018.4.x or v2019.x, they are not going to work anymore. This occurs due to a change in the Quartz.NET validation code. Please make sure your cron expressions are valid before updating your environment. See here details on how to proceed.
  • Deleting all versions of a library in bulk does not remove them all, as one version always remains in the database and is displayed in the user interface.
  • A user without View permissions on Schedules is able to see schedule-related alerts.
  • When using Azure Storage for package feed storage, uploading a package from Orchestrator resulted in the blob access policy being changed from Private to allow anonymous read access.

Bug Fixes


  • The performance of making POST calls to the /odata/Tenants endpoint has been improved, especially when dealing with large deployments.
  • The performance of disabling a tenant has been optimized, especially when dealing with a large number of users.
  • The performance of adding a large amount of Attended Floating Robots through POST requests to the /odata/Robots endpoint has been improved.
  • The performance of executing GET requests on the /odata/Environments(id) endpoint has been improved, especially in environments with a large amount of Robots.
  • Occasionally, due to a dynamic allocation issue, Robots stopped executing jobs assigned dynamically, and remained stuck in a pending state.
  • We've identified and remedied a drop in performance when deploying more than 500 Attended Floating Robots on a single machine template.
  • Multiple quartz triggers were generated in the database for non-existing jobs. This had a detrimental effect on the performance of the scheduling functionality.
  • Occasionally, in poorly performing networks or Orchestrator instances, the user was not logged out of the application after clicking Log Out.
  • The performance of the database notification distribution process was impaired in the context of thousands of alerts being generated at once. For this reason, a timeout exception was occasionally logged as well. Click here for a maintenance solution which may prevent further performance issues and can improve the SQL database response times.
  • Occasionally, due to deadlocks in the database, Robots stopped executing jobs, despite being available.
  • The mechanism behind background jobs has been optimized.
  • An error message was displayed when you tried to create a Robot on a previously defined machine. This only occurred in the context of a poorly performing internet connection.
  • Alerts were displayed with a delay of several minutes after being generated.
  • An error message was displayed when you tried to search for a value on the Robots page. This only occurred in the context of a large Robot deployment.
  • The Application Pool stopped if you uploaded multiple versions of the same package in environments that used the Azure, AWS, or Minio blob storage.


  • Refreshing twice the Manage Users or Manage Environment window cleared all selected entries while still displaying the row count according to the previous selection.
  • Sorting by name or surname did not work on the Users page if at least one user on the list had neither a name nor a surname, respectively.
  • Several synchronization issues were taking place when importing AD users, thus causing incorrect user-role association.


  • Searching for a process on the Start Job window did not return all the results containing the searched string. Furthermore, processes matching exactly the used query were not displayed first.
  • If you started a job on a Robot with no configured execution settings, Orchestrator automatically configured them to false.
  • The Latest button on the View Process window did not work correctly for semantic package versions if you used an external feed. Under the exact same conditions, for processes set to use older versions, the corresponding icon was not updated accordingly.
  • Any changes made to the Logging Level and Allow Development Logging options on the Settings tab were not taken into account when starting processes from the Robot tray. This occurred only if the processes were started before the Robot had sent a heartbeat.
  • An error message was displayed when you tried to edit the parameters of a process immediately after changing its version.
  • Uploading a package larger than the IIS size limit now returns the following error message: "The file you're trying to upload is too big. Please contact your administrator." Take into account that the limit is by default set to 28.6 MB.
  • The StopStrategy parameter on the Audit Data window was set to Kill for a newly created schedule without a stop strategy defined.
  • An error message was displayed when you tried to display the audit details for an action which was performed in a different organization unit.
  • An error message was displayed when you tried to create an asset of type Bool, if its name contained Japanese characters.


  • A user with the Robot role was prevented from accessing the Settings page, even if the role has View permissions on Settings by default.
  • The Upload, Renew and Delete buttons on the License page were not displayed unless having Edit permissions on Settings.
  • The Delete button was disabled whenever adding or removing the Administrator role from the current user.
  • Errors generated by the /odata/Permissions endpoint were logged with both Orchestrator and Orchestrator.BusinessException sources. Now, they are properly logged only under the Orchestrator source.


  • The RolesList parameter was not populated if you made GET requests to the /odata/Users(Id) endpoint.
  • POST calls to the /odata/HostLicenses/UiPath.Server.Configuration.OData.DeleteTenantLicense endpoint did not return 400 Bad Request, although the provided tenant Id did not exist.
  • Fixed an issue that prevented the 404 Not Found error message from being returned if you performed a POST request to the /odata/HostLicenses/UiPath.Server.Configuration.OData.SetTenantLicense endpoint and provided an invalid tenant Id.
  • The body of GET requests to the /odata/Robots/UiPath.Server.Configuration.OData.GetUsernames() endpoint did not include the @odata.count annotation in the response.
  • Robots could not download packages if you updated the tenant name using a PATCH call to the /odata/Tenants(id) endpoint.

User Experience

  • It is no longer possible to delete organization units if they have at least one user associated with it.
  • An error message is now displayed if you create a webhook with a target URL whose SSL certificate cannot be verified.
  • Columns on the Schedules page disappeared when you resized the browser window.
  • The left-hand menu disappeared from the screen if you pressed the Escape key.
  • Switching between organization units on the Robots page caused the Machine filter to be removed.
  • Occasionally, when creating a duplicate Robot using the Create Another feature, no radio options on the Settings tab were saved from the first configuration.
  • An error message was seldom displayed when you refreshed the License page for both the Attended and Unattended scenarios.
  • Changing the tenant timezone caused a one-day discrepancy between the dates on the License Usage graph.
  • Fixed an issue that obstructed incoming traffic to an Orchestrator instance, if the URL contained a custom suffix. Instead, the user was redirected to the original Orchestrator URL.
  • The Open Alerts Preferences icon for the Alerts drop-down was not displayed if you opened your Orchestrator instance in Internet Explorer.
  • You were not able to navigate through the search results in a drop-down list by using the arrow keys. This only occurred in Internet Explorer.


  • Uninstalling Orchestrator now removes the entire contents of the Activities folder, even if it contains custom files.
  • To ensure a smooth experience in offline environments, the list of activity dependencies has been updated in all our installers. Please note that as a result, the size of the artifacts has increased.
  • An error message was displayed if you closed the UiPathPlatformInstaller.exe wizard while the installation process was being executed.
  • Fixed an issue that prevented UiPathOrchestrator.msi from preserving your custom location, website and application pool names. Starting with v2019 Fast Track, all future updates of Orchestrator keep your previous custom values.

Updated 3 months ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.