orchestrator
latest
false
  • Release notes
UiPath logo, featuring letters U and I in white

Orchestrator release notes

Last updated Nov 25, 2025

November 2025

November 25, 2025

MCP Servers in general availability

We are excited to announce the general availability of two MCP Server types, a powerful new capability that introduces the emerging Model Context Protocol (MCP) to the UiPath® Platform. MCP enables seamless interoperability between LLMs or agents and automation tools, enabling greater reach, flexibility, and control in your automation workflows.

With this release, two types of MCP Servers are now generally available:
  • UiPath: Expose UiPath artifacts as tools via MCP. You can build a UiPath MCP Server directly from the platform interface.
  • Remote: Connect to external MCP Servers outside UiPath via secure tunneling.

For more information on this functionality, check the following pages from the Orchestrator user guide:

November 24, 2025

Improved Deploy package listing

We improved the Deploy package listing experience to make package management more usable and visually consistent across different screen sizes.



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.

November 20, 2025

Improved asset access during API Workflow debugging

As part of the API Workflows general availability, the Orchestrator API now returns asset values during API workflow debugging for any folders the current user can access, provided they can open a debugging session.

For more information, check the API workflows general availability release notes.

November 10, 2025

Improved experience when configuring advanced robot options

To ensure valid configuration, the Resolution Width, Resolution Height, and Resolution Depth fields can no longer be set to 0 when configuring advanced robot options.
If you attempt to enter 0 for any of these fields, the Submit button will now be disabled, preventing invalid form submission.

Linking execution settings for packages

You can now bind execution settings directly to packages of type Process and Agents. This allows you to define the configuration with which a process runs, including runtime type, account, and machine requirements at the package level, ensuring processes run in the right environment.

This feature is especially useful for complex automations that trigger other automations. It ensures that each automation can run on different infrastructure than its parent process.

For more information, check the Managing packages requirements page.

New authentication option for Amazon S3 storage bucket

You can now authenticate to your Amazon S3 storage bucket using an Integration Service connection.

This new authentication option simplifies setup and provides additional flexibility through credentials managed in Integration Service.

This new authentication method provides the following benefits:
  • Use an Integration Service connection to authenticate your Amazon S3 storage bucket.
  • Access multiple authentication types available through Integration Service connections:
    • Access key

    • Access key assume role

    • UiPath Managed Cross Account Assume Role

  • Authenticate using an existing Integration Service connection or create a new one directly during configuration.

For more information on how to create a storage bucket, check the Managing storage buckets page.

New credentials store integration: CyberArk® Conjur (read-only)

We added support for CyberArk® Conjur (read-only) as a credential store in Orchestrator.

This new option allows you to connect to your private CyberArk Secrets Manager, Self-Hosted or CyberArk Secrets Manager, SaaS application and securely retrieve credentials.

This integration provides the following key benefits:
  • Supports both API Key and Jwt authentication: you can choose between API key-based authentication or token-based authentication using a JSON Web Token (JWT) issued by UiPath or an external identity provider.
  • Enhanced flexibility: integrate with short-lived token systems for stronger, more adaptable security.
  • Consistent experience: configuration is similar to the existing CyberArk Conjur Cloud (read-only) store, making it easy to set up and manage.

November 4, 2025

UiPath Platform transition for Community users

Starting this week, Community users are being gradually migrated to UiPath Platform, a new automatic update system that keeps UiPath components (Studio, Assistant, Robot, and Browser Extensions) always up to date. The transition has the following impact for Orchestrator environments.

  • After migration, the following fields will display the Non-Compliant status. This is a known issue and will be fixed in a future update:
    • The Version status field from the Tenant > Machines page.
    • The Version status field from the Tenant > Machines > installed Versions & Logspage.
    • The Version status field from the Tenant > Monitoring > User sessions page.
  • UiPath Platform updates are fully managed by UiPath and cannot be controlled via Orchestrator policies.
  • UiPath Platform delivers Short-Term Support (STS) versions, while Orchestrator auto-update manages Long-Term Support (LTS) versions.
  • STS and LTS installations are not compatible on the same machine.

For more details and the Community rollout announcement, check the forum post: UiPath Platform - Automatic Rollout for Community Users.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo
Trust and Security
© 2005-2025 UiPath. All rights reserved.