23 March 2023
Event triggers as package requirements
We've tamed Orchestrator to identify the event triggers activities as package requirements at process-creation time. Associate them to an Integration Service connection, and make further configurations to comply with your business needs, all for the greater good of triggered automations.
22 March 2023
Live streaming and remote control
Remote debugging of job executions is now a friendlier affair with the help of our new one-stop-shop solution: live streaming and remote control. This allows you to watch an unattended execution while it is happening, and, if problems arise and debug is needed, to take remote control of the execution and try to fix it.
This new feature helps save time when identifying and resolving issues, and it reduces the number of manual interventions needed for debugging and unblocking unattended automation processes.
21 March 2023
Execution settings for Studio Web triggers
Studio Web triggers are now automatically disabled if the execution of their associated job fails 5 times consecutively. This action is available for time, queue, and event triggers, and is determined via API.
Note: it only applies to newly created triggers - existing triggers continue to behave the same.
This change brings with it a new alert that you can subscribe to: Trigger automatically disabled after failed job execution with the Fatal severity level.
The Trigger automatically disabled alert has been renamed to Trigger automatically disabled after job creation failures.
Responses from calling the
/odata/Foldersendpoint now contain the folder type property, which is read-only.
The maximum allowed storage size for job input/output arguments will soon be changed to 1 MB. If you need any more than that, we recommend that you use storage buckets.
Important: This will be enforced in May for Community users, and in November for Enterprise users.
Webhook events for jobs and queue items now include more properties:
SpecificPriorityValue for job events
ProcessingExceptionTimestamp and CreatorUserId for queue item events
Editing a postpone date for a queue item used the UTC value instead of the tenant time zone value.
Job execution video recordings were not deleted after 7 days, per our retention period.
14 March 2023
New date formatting library
We have switched to a new date and time formatting library, aiming to provide more unity around formats across locales. While this change has no impact on your experience whatsoever, you might notice the following improvements as compared to our previous library:
Date and time formats are now consistent across all locales, i.e. the same digit/letter combination is used throughout. For example, the English
2/24/2023, 4:48:25 PMis displayed as
2023/2/24 16:48:25in Japanese, whereas you would see
2022年7月5日 09時20分37秒before this change.
The elapsed time in seconds is now displayed as a precise number rather than an estimate, i.e.
10 seconds agoinstead of
a few seconds ago.
8 March 2023
Time triggers calendar update
We have removed the restriction to only create non-working days calendars on time triggers that had the same time zone as the tenant they belong to. From now on, any calendar you add to a trigger is interpreted as being aligned to the trigger's time zone.
6 March 2023
Exporting jobs grids
Ever wanted to create dashboards and metrics based on your jobs data? Nothing stands in your way, as you can export all of your job reports from the current folder and download them to your machine. Read more about Exporting grids.
See permission information
As an administrator, when creating or editing roles, you can now check what areas each permission controls. The information is displayed in a tooltip when you hover over the checkbox for a permission.
This can help you broadly decide if a permission is needed or not, judging by the Orchestrator areas to which it allows access.
For more information, see .
Serverless jobs news
Serverless jobs and test case executions now provide details on the robot size and consumed robot units.
1 March 2023
Host feed changes
The URL of the official host feed for packages will be changed to
and the Myget feed will be deprecated. This change will be applied in one week for
Community users, and two weeks for Enterprise users.If you are using a
firewall, make sure to add
https://pkgs.dev.azure.com to the allow list.
Otherwise, you will no longer be able to download official UiPath libraries.Update -
1 March 2023: For Enterprise users, the target date for this change has
been pushed to 27 April.
Video job recording
You can now benefit from an extra layer of efficiency when troubleshooting jobs. This is due to our new video recording feature, which is available at the process level for all unattended executions (currently only available as preview).You can choose to either record all jobs or only those that are failed, and you have access to these recordings for up to 7 days.The feature is only available for Automation Cloud Robots - Serverless at the moment, but will shortly be enabled for Automation Cloud Robots - VM as well.
The release of this feature brings about a change in the existing screenshot option: it is now available to all users, not only to those on the Enterprise plan.
When can I see these changes?
The date when a change is first announced in the release notes is the date when it first becomes available.
If you don't see the change yet, you can expect to see it soon, after we roll out changes to all the regions.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
- 23 March 2023
- Event triggers as package requirements
- 22 March 2023
- Live streaming and remote control
- 21 March 2023
- Execution settings for Studio Web triggers
- Bug fixes
- 14 March 2023
- New date formatting library
- 8 March 2023
- Time triggers calendar update
- 6 March 2023
- Exporting jobs grids
- See permission information
- Serverless jobs news
- 1 March 2023
- Host feed changes
- Video job recording
- When can I see these changes?
- Deprecation Timeline