Orchestrator release notes

We improved accessibility across several user interface components to support better usability.

When starting a job, the first available process in the list is now automatically selected based on name ordering.

This change streamlines the job start flow and reduces the number of steps required when launching jobs.

Starting a job using Run Agent now returns a clearer error message when the required Robot permissions are missing.

The error message now clearly indicates when the failure is caused by missing permissions to start a job, helping you identify and resolve configuration issues more quickly.

You can now delete video recordings directly from the More Actions context menu.

Previously, the Delete recording option was only available in Job Details, which made it harder to discover. This update improves usability by making the action easier to access.

OData APIs now include additional information in error responses when a request contains invalid or malformed query parameters.

You can now remove per-user and per-robot asset values more safely and efficiently when editing an asset.

When removing a value, a confirmation dialog is displayed to help prevent accidental deletions. The dialog displays the name of the user or robot whose value is about to be removed.

You can also select multiple values and remove them at once using the Remove button in the asset values grid.

Both columns are hidden by default and can be enabled through the column visibility settings, allowing you to view when a transaction item was created in either relative or exact timestamp format.

Deleting roles in Manage Access → Roles now includes an improved confirmation modal.

When deleting a role, you must type the role name to confirm the action. This helps prevent accidental deletions and provides clearer guidance about the impact of removing a role, including the effect on users who currently have the role assigned.

This event helps you monitor retry activity and react to queue items that are automatically or manually retried after a failure.

You can now remove per-user and per-robot asset values more safely and efficiently in the Assets editor.

When you delete a value, a confirmation dialog is displayed that includes the name of the affected user or robot, helping prevent accidental deletions.

You can also select multiple values and remove them at once. The grid now supports multi-selection, and when you choose Remove selected, the system displays a confirmation dialog describing how many entries will be removed.

We fixed an issue where the Advanced robot options status on the Check Access page did not update correctly.

Previously, after reverting a user’s advanced robot options from Custom back to the default configuration, the Check Access page could still display the status as Custom instead of None. The page now correctly reflects the current configuration state.

The secret remains visible when editing a webhook, and it can still be retrieved through direct API calls, as backend behavior has not changed.