Orchestrator release notes

As part of the organization creation flow, a new robot account, Default Robot, is now automatically added to all newly created organizations.

The account is included in the Automation Users group and is provisioned in all tenants of the new organization. Within each tenant, it is assigned to the auto-created Shared Folder with the Automation User role.

This setup provides out-of-the-box Unattended automation support for new organizations and their tenants.

You can now select System Administrator in the User filter on the Tenant > Audit page.

When creating a custom tenant role, you can now grant Solution deployments and Solution packages permissions to the role.

Password complexity settings are no longer syncronized between Orchestrator and Identity Server. To edit the settings, use the Identity Server APIs or the Admin Portal user interface.

We know that streamlining your database is as important to you as it is for us. This is why we are taking our retention policies up a notch by adding the option to delete or archive non-terminal state jobs and queue items.

This new option is integrated in the existing retention policy component at the process level for jobs, and at the queue level for queue items. It is available via a new set of fields dedicated to uncompleted jobs and queue items, respectively.

The default values for jobs and queue items are as follows:

For all your test data management efforts, use Test Manager.

The Allow to be Automation Developer role now has the Solution packages permissions View, Edit, and Create enabled by default.

The Folder Administrator role was missing the View, Edit, and Delete permissions for Test Case Execution Artifacts. We have fixed the issue.

You can choose to auto-refresh logs at a ten-second interval for jobs that are not either in a Pending state or in a final state. The option is available in the Logs section of the job side panel. For more information, see Viewing job logs.

Orchestrator now allows you to create disconnected event triggers, which you define from scratch, outside of an existing process. The new functionality, previously available in Integration Service, complements the existing Orchestrator capability to edit connected triggers defined as package requirements for a process. Therefore, Orchestrator now provides a unified trigger experience, enabling you to create and manage all types of triggers.

For details on creating disconnected event triggers, refer to Creating an event trigger.

When you create a new Orchestrator storage bucket, you can now enable file encryption via the Store in encrypted format option. For more details, check Creating storage buckets.

We have improved the precision of robot log timestamps, which now use microseconds instead of milliseconds. As a result, you should no longer encounter out-of-order logs for events that occur in rapid succession. Note that the change does not apply to already uploaded robot logs.

We extended the support for environment variables detection across all asset types, with the exception of credentials.

With this update, detection now also applies to assets of type integer, boolean, and text.

This enhancement broadens the range of assets that can automatically provide environment variables, reducing manual setup and improving consistency.

For more information on assets, check the Asset Types section.

Attempting to submit a single-step form with errors now highlights the first field where an error is detected.

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.

We enhanced the experience of working with Runtime Arguments when starting a job:

For more information on how to start a job and add arguments, check the page.

Orchestrator now determines the package type for packages published or uploaded via UiPath® means, such as packages published from Studio or uploaded to an internal feed, and displays them under the appropriate category for each type.

To leverage the new capability, we have made the following changes to the Orchestrator interface:

You can now view web apps published from Studio Web by using one of the following options:

You can now rename single files when uploading them to a storage bucket.

Orchestrator now provides you with a streamlined way of executing jobs through a third-party application of your choice.

To that end, we are introducing API triggers, a means to generate an API endpoint that allows you to run a job from an external application. All you need to do is create a trigger based on a process, copy the resulting URL, paste it into your tool, and authorize the request - this will run the job with the parameters you define.

These are the new items that you'll notice in the interface as part of this launch:

Find out more general information about API triggers, learn how to manage them, then see how to run a job via an API trigger.

You can now start a job using the Run as Myself (Personal automation) option if your user inherits appropriate tenant-level and folder-level access configurations from a group that the user is part of. Previously, you could use the Run as Myself (Personal automation) option to start a job only if an administrator had assigned a specific access configuration to your user in that folder.

We added support for a new asset type, Secret, for Solutions.

The Secret asset type works like the Credential asset type, but it is designed to store other sensitive values, such as API keys. You can enter the secret value directly in the Secret field.

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:

For more information, see Starting a job.

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

You can now track the instances when the trigger failed to start jobs from the new History tab. This feature helps you better understand and troubleshoot trigger behavior.

For more information, check the Trigger details page.

We have changed the behavior around initiating updates during job execution. As such, the Robots application no longer forces an update to a new version if a job is still running. Furthermore, during an update, active Robots enter a maintenance mode, ensuring they do not take on any new jobs until the update is complete.

This change also means that the 10-minute wait time for service-mode Robots is no longer applicable.

You can now select and upload multiple files to a storage bucket at once.

Unified Pricing is here! Our enhanced licensing model for Orchestrator offers new plans and a flexible credit system using Platform Units. Enjoy easier tracking and reallocation of resources for Orchestrator.

We removed the CreationTime field from the assets audit logs, as it was incorrectly included. The AuditTime field remains unchanged and is the correct value to reference.

On the Audit and Test Automation Audit pages, selecting View Details for an item now displays the audit information in the Audit Data panel.

In case the request for the audit logs total count fails, an error icon displays in the lower-left corner of the Audit grid. Hover over the icon for additional details on the error.

High density view is now enabled permanently, and the option to configure the setting is no longer available.

The audit log now specifies the reason for automatically disabling a trigger in the following scenarios:

In the Start Job window, if the job cannot start because a suitable account is not assigned to the folder, you receive an error message explaining the issue. Also, the Assign an account to the folder button is highlighted.

Additionally, selecting Assign an account to the folder now allows you to create a new account on the fly and assign the appropriate roles to the account. You can then resume the Start job workflow.

For further information, refer to Starting a job.

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

For further information, refer to About jobs.

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

For further information, refer to Tenant feed.

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.

We have enhanced the Job details tab to make the input and output move visible.

Additionally, the Runtime details section of the tab now provides more detailed information.

For more information, refer to Viewing job details.

In the Orchestrator side panel, you can use the middle click function on your mouse to open a folder in a new browser tab.

When you navigate to Tenant in the user interface, Monitoring is now displayed as the landing page.

The Transactions page now includes two new options: View creator job and View executor job, which display information about the job that created or executed the queue item. For more details, refer to Transactions overview.

When you run or publish a solution created in Studio Web, the Process name column in the Jobs grid now displays [Publish] for the corresponding entry. Previously, this column displayed Generic Process as the default job process name.

To better identify the status of a Personal Workspaces folder, the side panel now displays this information when you select a folder.

To align with the high-density view, we removed all menu icons at the tenant and folder levels.

We removed the real count hint from the Logs page and now display only 10,000 items. This change helps maintain a clean and efficient user interface.

We have improved our time filters with a wider selection or predefined intervals and the addition of custom intervals.

Additionally, you can select the Custom option and set the exact date and time for both the start and the end of your interval.

The favicon for UiPath® has been updated to reflect the latest UiPath logo, ensuring a consistent visual identity across browser tabs.

On the tenant-level Monitoring screen, under Unattended sessions, you can now display the running, stopping and terminating jobs for each machine in a side panel. For more information, refer to Unattended sessions.