- 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 packages
You can now bind execution settings directly to packages of type Process. 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.
Enhanced Input/Output argument display in job details
When viewing Input or Output arguments in the Job Details sidepanel, large payloads are now handled more efficiently and displayed in an improved read-only editor.
Arguments that exceed a certain size are now backed by remote storage as files and partially loaded in the interface for faster access. The content is initially truncated up to a certain size limit, with the option to expand and load the full file. You can also download the full content.
The Copy option remains available for content within a certain limit, while the Download option is always accessible for larger inputs and outputs. These updates ensure better performance, readability, and reliability when working with large job arguments.
Increased input payload limit for manually started jobs
The maximum input payload size for jobs started manually from Orchestrator has been significantly increased. Previously, large payloads could not be processed due to a strict character limit. With this improvement, larger arguments are now backed by remote storage.
- November 24, 2025
- Improved experience when configuring advanced robot options
- Linking execution settings for packages
- New authentication option for Amazon S3 storage bucket
- New credentials store integration: CyberArk® Conjur (read-only)
- November 6, 2025
- Enhanced Input/Output argument display in job details
- Increased input payload limit for manually started jobs
