April 2026

April 1, 2026

Note:

The release happened on March 25, 2026. Release notes were published later, due to delays.

Accessibility improvements

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

Automatically preselect the first available process when starting a job

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.

Clarified error message for missing Robot permissions

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.

Delete recording option added to More Actions menu

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.

Detailed information for OData validation errors

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

Error responses now contain a Details field that provides a more descriptive explanation of the validation error.

Improved removal of per-user and per-robot asset values

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.

New Created columns added to transaction items

We added two new option columns to the queue transaction items grid:

• Created: displays the time elapsed since the transaction items was created.
• Created (absolute): displays the exact timestamp when the transaction item was created.

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.

New delete role confirmation modal

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.

New QueueItem.retried webhook event

A new webhook event, QueueItem.retried, is available. An event is triggered whenever a queue item is retried.

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

Remove per-user and per-robot asset values more safely

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.

Fixed Advanced robot options status on the Check Access page

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.

Fixed webhook secret visibility with webhook.view permission

Users with the webhook.view permission can no longer expose webhook secrets through network requests when accessing the Webhooks listing page.

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