Orchestrator release notes

DELIVERY:

Last updated Apr 17, 2025

April 2025

April 17, 2025

Improvements to removing machines and unattended sessions

We made the following improvements to removing machines and deleting unresponsive or disconnected unattended sessions:

You can now delete machines that have time triggers or queue triggers attached. Previously, deleting a machine that had triggers attached was possible only for event triggers or API triggers.
You can now unassign multiple machines from the Machines grid simultaneously at folder level. Previously, you could only unassign machines from the Machines grid individually.
You can now delete unresponsive or disconnected unattended sessions that have time triggers or queue triggers attached. Previously, deleting an unattended session that had triggers attached was possible only for event triggers or API triggers.

For further information, refer to the following documentation:

The improvements include a new Trigger configuration was changed notification. You receive the notification in the interface and via email in the following scenarios:

Deleting machines or unassigning them from folders removes all the machines for a trigger that is already disabled.
Deleting machines or unassigning them from folders removes some but not all the machines to which an enabled trigger is attached.

Improved runtime allocation checking

If you attempt to update the number of runtimes allocated to a machine template to a lower value than the number of jobs currently executing on any machine connected to the template, you receive an error message.

Authenticating feeds using JWT bearer tokens

You can now use the built-in nuget.exe authenticator to specify personal access tokens and other JWT bearer tokens for authenticating your feeds. For more information, refer to Settings.

Strong confirmation on delete always enabled

To avoid accidental deletions, strong confirmation on delete is now always enabled, and the option to disable it is no longer available.

Interface updates on the Packages pages

We have made the following changes in the Packages tab under Tenant:

We have renamed the Workflow tab to RPA.
A new Workflow type column is available in the tenant view, under Packages, in the RPA tab. The new property can have the following values:
- RPA - indicates an RPA package.
- Unknown - indicates an unknown package, such as packages created with older versions of Studio or unknown NuGet packages imported from a package feed.
Additionally, the grid now includes a Workflow type filter with the following values: All, RPA, and Unknown.

For further information, refer to Tenant feed.

Interface updates in the Jobs grid

We have made the following changes to the Jobs grid under Automations, at folder level:

We have changed the order of the columns in the grid and hidden the following columns by default: Machine, Hostname, Host identity.
The grid now includes a Duration column displaying the duration of each job that reached a final state.
We have renamed the Job type column to Execution type.

For further information, refer to About jobs.

Bug fixes

An issue occurred if you upgraded a process while jobs that executed it were suspended, and the process upgrade involved changing the target framework from Windows - Legacy to Windows. In this scenario, the jobs failed when you resumed them. The issue no longer occurs.
Queue items appeared as successful when they had a false processing status and an absent ProcessingException. This scenario now results in a BadRequestException with an InvalidRequest message.

April 7, 2025

Entry point selection when starting a job temporarily not possible

We recently announced a new feature that allowed you to select the entry point when starting a job.

However, due to a bug, we temporarily disabled the feature. We are working on re-enabling it soon.

April 2, 2025

Selecting the entry point when starting a job

Note:

Erratum - added April 7, 2025

We temporarily disabled the feature due to a bug. We are working on re-enabling it soon.

For processes that have multiple entry points, you can now select the entry point to use when you start a job via one of the following options:

The Start a Job button under Automations, in the Processes grid:
The Start a Job Now button under Automations, in the Triggers grid:

For more information, see Starting a job.

Introducing the User interaction process property

We have replaced the foreground and background process icons with a User interaction column, which is available in the folder view, under Automations, in the Processes and Jobs grids. For foreground processes, the value of the User interaction property is Required, while for background processes, the value is Not required. As an additional benefit, you can filter processes by User interaction.

For additional information, refer to About processes and About jobs.

On this page