- Automation Suite on Linux Release Notes
- Automation Suite on EKS/AKS Release Notes
- Automation Suite on OpenShift release notes
2.2510.3 release notes for Automation Suite on OpenShift.
Release date: July 23, 2026
Product sizing improvements
We have optimized the minimum hardware requirements for Automation Suite products such as Integration Service and Document Understanding. To check the hardware requirements for deploying Automation Suite 2.2510.3, refer to the capacity planning calculator.
Installing Automation Suite without cluster-scoped permissions
You can now install Automation Suite without granting the installer service account (uipathadmin) any cluster-scoped permissions (ClusterRole or ClusterRoleBinding). This flow uses namespace-scoped roles only, with a cluster administrator performing the compensating actions that require cluster-scoped access.
For details, refer to Granting installation permissions without cluster roles.
Configurable concurrency limit for Automation Suite Robots
You can now explicitly define the maximum number of jobs that can run concurrently in Automation Suite Robots. Previously, Automation Suite Robots used get and list permissions on nodes to determine this limit, which are not available in clusters with strict RBAC policies.
To configure the maximum number of concurrent jobs, set concurrency_limit in the asrobots section of input.json. For details, refer to Automation Suite Robots-specific configuration.
Improved certificate validation error messages
We have improved the error messages returned during prerequisite certificate validation. Checks now report the exact failure, such as incorrect chain order or certificates not belonging to the chain, instead of a generic message.
uipathctl improvements
- The
uipathctl manifest apply --dry-runcommand no longer requires confirmation. Previously, running this command prompted for confirmation. - You can now use the
--nodeflag withuipathctl prereq runto control which node runs the per-node prerequisite checks. Use--node anyto run the checks on any available node without pinning to a specific node,--node <node-name>to run the checks only on that node, or--node all(default) to run the checks on every node, as before. For details, refer to uipathctl prereq run. - You can now configure CPU and memory requests and limits for workloads created by
uipathctl, such as those used for health checks, prerequisite checks, support bundle generation, migrations, and upgrades. Use theworkload_resourcesparameter ininput.json, or the--probe-cpuand--probe-memoryoptions for commands that support them. For details, refer to Configuring resource requests and limits for uipathctl-created workloads.
Romanian language support
The Automation Suite user interface is now available in Romanian.
Bug fixes
- We have fixed an issue where Studio Desktop failed to load Integration Service connectors and activities due to a routing misconfiguration in the
intsvcs-periodicVirtualService. - An issue caused the prerequisite checks command to incorrectly fail when Document Understanding modern projects was enabled and AI Center was disabled. We fixed the issue.
- This release includes the fixes delivered in Automation Suite 2.2510.2+patch1.
- This release includes the fixes delivered in Automation Suite 2.2510.2+patch2.
Known issues
Maestro instance management page rendering issue
Erratum - added July 24, 2026: If Insights is enabled on the customer cluster, the Maestro instance management page does not render all information correctly unless the global.insightsRtmEnabled global feature flag is also enabled.
To enable the flag, in ArgoCD, open the Maestro application, select Details, then the PARAMETERS tab, and search for the global.insightsRtmEnabled key. Set its overridden value to true, exit the tab, and wait for ArgoCD to sync. If ArgoCD does not sync automatically, select Sync in the Maestro application.
Kerberos authentication limitations
Kerberos-based authentication is 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.
MessageBus schema migration fails on databases seeded from Automation Suite 2022.10.x or earlier
When upgrading to Automation Suite 2.2510.3, the MessageBus schema migration fails if the database was originally created on Automation Suite 2022.10.x or earlier, regardless of how many versions it has been upgraded through since. Databases originally created on Automation Suite 2023.x or later are not affected.
To check whether your database is affected, run the following query:
SELECT * FROM [msgbus].[__EFMigrationsHistory] WHERE MigrationId NOT LIKE '2[0-9][0-9][0-9]%'
SELECT * FROM [msgbus].[__EFMigrationsHistory] WHERE MigrationId NOT LIKE '2[0-9][0-9][0-9]%'
If the query returns any rows, delete them before upgrading:
DELETE FROM [msgbus].[__EFMigrationsHistory] WHERE MigrationId NOT LIKE '2[0-9][0-9][0-9]%'
DELETE FROM [msgbus].[__EFMigrationsHistory] WHERE MigrationId NOT LIKE '2[0-9][0-9][0-9]%'
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.3.
Legend:
✅ New: This Automation Suite version includes a new product version. New release notes are available.
◆ Bundled: This flavor includes a previously released product version. No new release notes are available.
- Product sizing improvements
- Installing Automation Suite without cluster-scoped permissions
- Configurable concurrency limit for Automation Suite Robots
- Improved certificate validation error messages
- uipathctl improvements
- Romanian language support
- Bug fixes
- Known issues
- Maestro instance management page rendering issue
- Kerberos authentication limitations
- FIPS 140-2 support limitations
- MessageBus schema migration fails on databases seeded from Automation Suite 2022.10.x or earlier
- Deprecation timeline
- Bundling details
- Product versions