- Release notes
Orchestrator release notes
Introducing Automation Suite Robots
With Automation Suite robots, you can now run background unattended automation and use high density robots without having to worry about constantly provisioning new machines yourself to provide robot computational power at scale.
Add the new Automation Suite Robots machine template to folders to make sure a machine and robot are always available when unattended jobs need to run.
Introducing indexes
You can now create indexes in Orchestrator, enabling efficient retrieval-augmented generation for UiPath generative AI experiences. Indexes act as vector database folders organizing business data embeddings to enhance semantic search, reduce hallucinations, and ground AI results in current, relevant information.
Indexes can be created in shared folders and are managed through the Context Grounding service. Data sources include storage buckets and Integration Service connectors, with customizable ingestion options for various file types.
For details, refer to Indexes.
Introducing coded agents
We now support agents that you build using code, enabling highly tailored automations with complex logic. By developing agents in your own IDE, you have full control over agent logic, behavior and system integration.
.nupkg packages and publish them
to Orchestrator via a package feed of your choice.
Once you deploy a coded agent to an Orchestrator folder, it behaves like any standard process. Therefore, you can schedule, trigger, and monitor agent execution, as well as integrate coded agents into broader automation workflows. For details, refer to Deploying agents. Additionally, UiPath SDKs provide logic to invoke and interact with UiPath resources directly from code: assets, queues, buckets, and more.
Secret asset type
As part of our coded agents rollout, we are making it possible to define environment variables that allow you to make configuration changes to your agent without modifying the code directly.
To assist you in providing environment variables such as API keys that your coded agent may require, we have added support for secret-type assets.
For more information, refer to About assets.
Agent traces
For agent process jobs, you can view the job trace in the job details panel, under a dedicated tab. The trace provides a comprehensive, hierarchical view of the job run, its input and output, as well as any other resources invoked or jobs executed in connection with the run.
The trace view also allows you to provide positive or negative feedback, as well as comments, on any of the trace items. For details, refer to Viewing job details.
Simplified header
We simplified the header to create a cleaner, more intuitive user experience. The main actions you use most often are now grouped together for easier access.
What's changed
- Searching for resources in a tenant
The Search button is now located next to the Tenant button on the left side of the screen. You can continue using it to search for resources in a tenant.
For more details, check the Searching for resources in a tenant page.
- Creating new
resources
The Create new button is now also next to the Tenant button on the left side of the screen.
To create a new resource, select the vertical ellipsis (⋮) button and choose the resource type from the dropdown list.
- Accessing My
Reports
The My Reports button has been moved next to the Tenant button.
Select the vertical ellipsis (⋮) button and choose My Reports from the list.
- Managing access
The Manage Access button has been removed from the header.
You can manage access directly from the Manage Access tab under the Tenant page.
Bug fixes
-
We fixed an issue where jobs were occasionally not displayed on the Jobs page after a manual start.
Previously, the newly started job would only appear after refreshing the page.
With this fix, jobs are now displayed in the Jobs list after a manual start, and the Job panel opens automatically as expected.
-
We removed the Async callback option from the Default call mode dropdown when creating an API trigger.
This option was not yet supported, even though it was previously displayed in the user interface.
