March 2023

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.

Read more about event triggers and learn how to configure them them.

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.

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.

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:

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.

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.

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.

Serverless jobs and test case executions now provide details on the robot size and consumed robot units.

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.