2.2510.2

Release date: April 15, 2026

New agentic capabilities onboarded to Automation Suite

We are continuing to expand the agentic automation capabilities available in Automation Suite on OpenShift. This empowers you to meet your data sovereignty needs while bringing agentic automation to life within your own infrastructure, in line with the capabilities available via Automation Cloud.

As part of this release, the following products and services are now available:

• Agents
• Autopilot
• Healing Agent
• Maestro
• MCP Servers
• ScreenPlay

Before enabling these products, refer to the cross-product dependencies and prerequisites to ensure your environment meets all requirements. Installation and configuration details are available in the Automation Suite on OpenShift Installation Guide.

TLS certificate chain validation

Automation Suite now requires a complete TLS certificate chain - a leaf certificate, all intermediate certificates, and the root CA. Previously, you could supply a partial chain (leaf certificate and root CA only). You must update your Certificate Authority Bundle to include all intermediate certificates. If you do not, TLS validation will fail.

For details, refer to Certificate requirements.

New mandatory field for disaster recovery deployments

We have introduced a new mandatory type field in the multisite section of input.json. This field is required when configuring disaster recovery deployments and specifies the deployment type. You must set it to active-passive. This field is required for both the primary and secondary cluster configurations.

For details, refer to Disaster recovery: Active/Passive configurations.

Improved prerequisite check messages for Object Store API validation

Object Store API prerequisite checks now provide clearer error messages, making it easier to diagnose and resolve configuration issues before installation.

Integration Service support for FIPS 140-2

Integration Service is now supported on Automation Suite deployments that run on FIPS 140-2-enabled machines. For details, refer to Security and compliance.

New Integration Service configuration for sovereign cloud deployments

A new optional queue_config.fqdn_suffix field is now available under integrationservices in input.json. This field is intended for sovereign or national cloud deployments where queue endpoints use a non-standard FQDN suffix, such as China AWS (amazonaws.com.cn) or China Azure (core.chinacloudapi.cn). If the field is left empty or omitted, default suffixes apply.

For details, refer to Configuring input.json.

Configurable Istio ingress gateway service name

The Istio ingress gateway service name, previously hardcoded as istio-ingressgateway, is now configurable using the istio_gateway_service_name parameter in the ingress section of input.json.

For details, refer to Installing and configuring the service mesh.

Extended product support for Active/Passive deployments

Autopilot for Everyone and Solutions now support Active/Passive deployments. For details, refer to Disaster recovery - Active/Passive.

Support for HashiCorp Vault and AWS Secrets Manager as secretstore providers

Automation Suite now supports two additional secretstore providers for storing sensitive credentials:

• HashiCorp Vault
• AWS Secrets Manager

For details, refer to Configuring HashiCorp Vault as a secretstore and Configuring AWS Secrets Manager as a secretstore.

Updated minimum External Secrets Operator version

We have updated the minimum supported version of the External Secrets Operator to v0.16.2 (Helm chart v0.16.2), which includes the ESO v1 APIs. For details, refer to Installing the External Secrets Operator.

Azure sovereign cloud support for Key Vault secretstore

We have introduced support for Azure sovereign cloud environments in the Azure Key Vault secretstore configuration. To connect to a sovereign cloud environment, you must configure the environment_type field. For details, refer to Configuring the Azure cloud environment.

Admin

User management role

Organization administrators can now delegate identity management tasks to non-admin users through a new custom organization-level role. When assigned, this role lets users manage user accounts, robot accounts, and local groups at the organization level without granting full organization administrator rights. The role supports granular CRUD permissions per resource type and includes built-in elevation-of-rights protections: users with this role cannot modify the Administrators group or interact with existing organization administrator accounts.

For details, refer to User management role.

Updated Bring Your Own Model experience

The LLM configuration experience has been redesigned to provide a simpler and more intuitive way to add and manage models. The updated interface introduces clearer configuration elements, including a mandatory API Type (endpoint type) selection, ensuring explicit alignment between the configured model and its supported endpoint.

With this update, you can securely connect UiPath agentic products to your own LLMs while retaining full control over model behavior, configuration parameters, capacity, and deployment architecture. Models remain within your environment, supporting strict security, compliance, and data residency requirements.

In addition, you can use custom connector templates directly from the configuration flow to integrate proprietary gateways, private endpoints, and non-standard APIs, enabling self-service onboarding of custom and private LLM infrastructures.

For details, refer to Configuring LLMs.

For an overview of supported LLM providers, integration modes, and capability compatibility by product and feature, see Large Language Model Support.

Correction - added May 11, 2026: As of Automation Suite 2.2510.2, Anthropic Claude LLMs must be configured using the Amazon Web Services connector in Integration Service. Existing connections created with the Amazon Bedrock connector in Automation Suite 2.2510.x must be migrated to the Amazon Web Services connector.

Expanded custom LLM configuration support

The following products, newly onboarded to Automation Suite, support custom LLM configurations: Agents, Autopilot, Healing Agent, and UI Automation.

Context Grounding updates

Context Grounding includes two new capabilities available through UiPath Agents:

• DeepRag enhances retrieval-augmented generation with deeper, multi-step reasoning over your knowledge sources, enabling agents to surface more accurate and contextually relevant information from complex or large-scale data.
• Batch Transformation allows large volumes of documents to be processed and prepared for grounding in a single pipeline run, reducing overhead and making it easier to keep agent knowledge bases current at scale.

Bug fixes

• We have fixed an issue that prevented the use of custom database names for Solutions. Previously, when you specified a custom database name, the prerequisite checks failed.
• We have fixed an issue that caused some AI Center and Document Understanding pods to fail to start when database TLS certificate verification was enabled.
• We have fixed an issue that caused the istio-validation-deployment deployment to not be automatically deleted after running the prerequisite checks (uipathctl prereq) or the health check (uipathctl health check), consuming unnecessary cluster resources.
• This release includes the fixes delivered in Automation Suite 2.2510.1+patch1.

Known issues

Kerberos authentication limitations

Kerberos-based authentication is currently not supported for the following products and services:

• Agent Hub
• Agents
• AI Trust Layer (LLM Gateway, LLM Observability, Context Grounding)
• Autopilot for Everyone
• Autopilot (A4D)
• Integration Service
• Maestro
• Semantic Proxy
• Solutions
• Studio Web
• TaaS

We are working on bringing Kerberos support to upcoming Automation Suite releases.

Meanwhile, you can use alternative authentication mechanisms such as basic authentication or workload identity-based authentication.

FIPS 140-2 support limitations

Insights is not supported on Automation Suite deployments that run on FIPS 140-2-enabled machines. To remain compliant with FIPS 140-2 requirements, you must disable Insights. If you need to use Insights, you can deploy it on a dedicated non-FIPS node.

For details, refer to Security and compliance and How to deploy Insights in a FIPS-enabled cluster.

Deprecation timeline

We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.

Bundling details

Product versions

The following table outlines the release status, version, and release notes for all UiPath products deployed under Automation Suite 2.2510.2.

Legend:

✅ - This Automation Suite version bundles a new version of the product. New release notes are available.

❌ - This Automation Suite version bundles a previously released version of the product. No new release notes are available.

Product	Product version	Release status	Release notes
Action Center	2.2510.2	✅	Action Center release notes
Agents	2.2510.2	✅	Agents release notes
AI Center	2.2510.2	✅	AI Center release notes
AI Computer Vision	2.2510.2	✅	AI Computer Vision release notes
Apps	2.2510.2	✅	Apps release notes
Automation Hub	2.2510.2	✅	Automation Hub release notes
Automation Ops	2.2510.2	✅	Automation Ops release notes
Autopilot for Everyone	2025.9.5	✅	Autopilot for Everyone release notes
Data Service	2.2510.2	✅	Data Service release notes
Document Understanding	2.2510.2	✅	Document Understanding AI Center-based projects release notes Document Understanding modern projects release notes
Healing Agent	2.2510.2	✅	Healing Agent release notes
Insights	2.2510.2	✅	Insights release notes
Integration Service	2.2510.2	✅	Integration Service release notes
Maestro	2.2510.2	✅	Maestro release notes
Screenplay	2.2510.2	✅	Screenplay release notes
Orchestrator	2.2510.3	✅	Orchestrator release notes
Solutions	2.2510.2	✅	Solutions release notes
Process Mining	2.2510.2	✅	Process Mining release notes
Studio Web	2.2510.2	✅	Studio Web release notes
Test Manager	2.2510.2	✅	Test Manager release notes