September 2026 release notes for Orchestrator in Automation Cloud.

You can now specify environment variables when deploying or editing an RPA (standard) process, using the same Environment Configuration field already available for agent processes. Enter a value directly, or reference a secret-type asset in the same folder to avoid storing the value in the field itself.

This requires Robot 25.10 or later, since earlier Robot versions don't read the environment configuration for RPA processes.

Environment variables configured this way are also captured when you export the process into an Automation Solutions package, so the values carry through install and upgrade. For details, see Managing Processes.

Turning a feature preview on or off in the Feature preview panel now applies immediately. The panel closes and the page reloads automatically, so you no longer need to select a separate reload action to see the change take effect.

When adding queue items in bulk, Orchestrator may now emit multiple queueItem.added events, each covering a subset of the uploaded items, instead of a single event containing all of them. Batching applies only to larger uploads.

Maestro BPMN, Maestro Case, and Maestro Flow processes and resources now show their own dedicated icons instead of the generic project icon, making them easier to tell apart wherever Orchestrator displays resource type icons. The menu entry that groups all three process types together also gets its own dedicated Maestro icon.

Each credential store now has a Folder access setting. Keep the default All folders to let any folder in the tenant use the store, or select Selected folders only to limit it to the folders you assign. The Stores page shows the current setting for each store in the new Restricted to folders column, and the Manage in folders action adds and removes folders in one step.

Each folder now has a Credential stores page listing the stores that folder can use, with an Access origin column showing whether access is assigned directly, inherited from a parent folder, or available to the whole tenant. A store assigned to a folder is inherited by all of that folder's subfolders.

For details, see Credential store folder access and Assigning credential stores to folders.

Agent Gateway is the new hub in Orchestrator for registering and managing the agents and servers that connect the platform to the outside world. It brings the existing MCP Servers area together with a new A2A Agents area, organized by protocol: Model Context Protocol (MCP) exposes capabilities as tools, and Agent2Agent (A2A) supports multi-turn conversations between agents.

This release also introduces A2A Agents. Register an agent hosted outside UiPath so it can be called from the platform, or expose a conversational agent you've already deployed so external A2A clients can talk to it, all with the same folder permissions, guardrails, and Traces visibility as the rest of the platform.

For details, see About Agent Gateway.

Platform MCP Servers let you expose a first-party UiPath service, such as Test Manager, as a curated set of MCP tools. Instead of exposing every operation the service offers, you choose which ones become tools, so a model only ever reaches the operations you approve.

For details, see MCP Server types.

Swagger MCP Servers turn any OpenAPI document into MCP tools, so you can expose an external API as MCP tools even when it has no MCP server of its own. Provide the document by URL or paste it directly, and each operation it describes becomes a tool.

For details, see MCP Server types.

The Cloud Robots, Elastic Robot Orchestration, and Automation Suite Robots documentation for Automation Cloud has moved from the Orchestrator guide to the Robot guide, for a clearer, more discoverable structure.

The Solution deployments, Processes, and Resources pages now include a Group by dropdown next to the Search field. Group results by Project, Folder, or Automation Type, or select None for an ungrouped list. After you apply a grouping, select Reset to defaults to return to the default view.

For details, see About the Registry context.

The Resources and Processes pages now display two additional columns, Labels and Properties, showing the tags and key-value properties assigned to each resource or process.

For details, see Resources and Processes.

The release of the Orchestrator Credentials Proxy 2.2.2 brings a series of updates:

We have also made a few important fixes:

For the software requirements and the new store's configuration sample, check the Orchestrator Credentials Proxy documentation.

You can now integrate AWS Secrets Manager as a credential store in Orchestrator through an Integration Service connection, in addition to the existing Access Key and Secret Key method. Select Connection as the Authentication type to use any authentication method supported by the Integration Service Amazon Web Services connector, including IAM role-based methods, instead of entering a long-lived access key and secret key directly in Orchestrator.

For configuration details, see AWS Secrets Manager integration.

We fixed an issue where duplicating a job with Dynamic Allocation selected and a machine template already assigned did not display the Hostname field. As a result, the duplicated job could run on any available host instead of the configured one. The Hostname field is now displayed correctly when duplicating a job.