- Release notes

Orchestrator release notes
Improved experience when configuring advanced robot options
0 when
configuring advanced robot options.
0 for any of these fields, the Submit
button will now be disabled, preventing invalid form submission.
Linking execution settings for Process 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.
- 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.
- 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.
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.
- November 10, 2025
- Improved experience when configuring advanced robot options
- Linking execution settings for Process packages
- New authentication option for Amazon S3 storage bucket
- New credentials store integration: CyberArk® Conjur (read-only)
- November 4, 2025
- UiPath Platform transition for Community users