Orchestrator release notes

A new Duplicate job action is now available for jobs. This option opens the Start Job form pre-filled with the original job’s configuration. The Duplicate job action replaces the Restart job action and enables the option for any state. Previously non-terminal states (Pending, Running, Stopping, Terminating, Suspended, Resumed) could not have been acted upon.

The webhook URL is now available on the Package Requirements page for event triggers, making it easier to access when needed.

We included a hint for the disabled VM option in the Unattended setup page to explain that VM configurations are not supported. The hint also includes a link to the relevant documentation. This is available for both UiPath-hosted and self-hosted unattended robots.

Queue triggers can now continue processing new queue items even when previously started jobs are in a Suspended state. This ensures that remaining items in the queue are picked up without requiring additional item uploads or manual intervention.

We introduced a Reset to default button for runtime arguments. This option lets you easily restore any field to its package or process default value. When restarting a job, this action resets values to their configured defaults, not to the values from the previous run.

We fixed an issue where personal workspace sub-folders were returned by the /odata/Folders API.

We fixed an issue where upgrade or rollback operations could fail with Error code - 1001, Message - "The name is already used" due to resources being recreated with the same name.

We removed the previously deprecated GetRobotAsset(robotId='{robotId}') endpoint. This endpoint was already marked as deprecated and is no longer functional. You can use the following endpoint instead: /odata/Assets/GetRobotAssetByNameForRobotKey.

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.

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

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.

We added two new option columns to the queue transaction items 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.

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.

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.

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.