2.2510.3

2.2510.3 release notes for Automation Suite on Linux.

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.

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-run command no longer requires confirmation. Previously, running this command prompted for confirmation.
• You can now use the --node flag with uipathctl prereq run to control which node runs the per-node prerequisite checks. Use --node any to 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 the workload_resources parameter in input.json, or the --probe-cpu and --probe-memory options 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

• 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.
• We have fixed an issue that prevented Fluentd from exporting logs in IPv6 environments. Previously, Fluentbit failed to forward logs to Fluentd due to the Fluentd forward input plugin binding to an IPv4 address by default.
• An issue prevented the monitoring section parameters in cluster_config.json from being applied to the monitoring stack. We fixed the issue.
• An issue prevented uipathctl from resizing an existing data disk partition (such as the Docker registry, monitoring, or Insights partitions) unless the underlying disk path was explicitly provided using the --volume flag. This behavior was incorrect, since uipathctl is designed to automatically detect the associated disk on subsequent runs without requiring --volume. We fixed the issue.
• We have fixed an issue where Studio Desktop failed to load Integration Service connectors and activities due to a routing misconfiguration in the intsvcs-periodic VirtualService.
• 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

Horizontal Pod Autoscaler and ArgoCD scaling conflict in HA environments

Erratum - added September 10, 2026: In HA environments, when load increases, the Horizontal Pod Autoscaler (HPA) scales the affected workloads up while the ArgoCD application controller scales them back down. This occurs due to ArgoCD treating the replica count defined in the Helm chart or manifest as the source of truth, causing the workloads to repeatedly scale up and down without stabilizing.

To address the issue, you must patch the argocd-cm ConfigMap in the <argocd> namespace so that ArgoCD ignores replica count differences:

kubectl -n <argocd> patch configmap argocd-cm --type merge -p \
  '{"data":{"resource.customizations.ignoreDifferences.argoproj.io_Rollout":"jsonPointers:\n- /spec/replicas\n"}}'

Reapply the command after every ArgoCD chart re-sync or Automation Suite upgrade, since both overwrite the ConfigMap and remove the patch.

We fixed the issue in Automation Suite 2.2510.4.

Pods stuck in Init state due to XFS volume mount failure on RHEL 8.x nodes

Erratum - added September 10, 2026: On RHEL 8.x nodes, TopoLVM formats new persistent volumes with XFS on-disk features (bigtime, inobtcount, nrext64) that the RHEL 8.x kernel and xfsprogs version don't support. Pods that request a new PVC, such as AI Center training pipeline pods, remain stuck in the Init state with a mount failed: wrong fs type, bad option, bad superblock error.

To address the issue, refer to Troubleshooting.

Kerberos KDC discovery fails in Active/Active deployments due to truncated DNS SRV responses

Erratum - added September 10, 2026: In Automation Suite Active/Active deployments on Linux (RKE2), Kerberos KDC discovery can fail during installation or upgrade, resulting in Integrated Authentication and LDAP errors. The issue occurs because the Kubernetes DNS Service exposes DNS resolution over UDP/53 only. When a Kerberos SRV lookup, such as _kerberos._tcp or _kerberos._udp, returns a response too large for UDP, the DNS client retries over TCP/53. Since the Kubernetes DNS Service doesn't expose TCP/53, the retry fails.

To address the issue, enable TCP/53 on the Kubernetes DNS Service:

1. Edit the rke2-coredns Helm chart configuration:

   kubectl -n kube-system edit helmchartconfig rke2-coredns
   

2. Under zone in spec.valuesContent, add use_tcp: true:

   servers:
   - zones:
     - zone: .
       use_tcp: true
     port: 53
   

We fixed the issue in Automation Suite 2.2510.4.

prune-telemetry CronJob fails after upgrading to Automation Suite 2.2510.3

Erratum - added September 10, 2026: After upgrading to Automation Suite 2.2510.3, the prune-telemetry CronJob in the uipath namespace fails on deployments that authenticate to SQL Server using Azure AD (Entra ID) Managed Identity, Default Azure credential, or Workload Identity authentication, with the following error:

Cannot find an authentication provider for 'ActiveDirectoryManagedIdentity'.
Install the 'Microsoft.Data.SqlClient.Extensions.Azure' NuGet package
to use Active Directory (Entra ID) authentication methods.

The issue occurs due to a missing dependency in the uipathcore container image. All CronJob retries fail with this error.

To address the issue, upgrade to Automation Suite 2.2510.4, or you can temporarily delete the failing CronJob:

kubectl delete cronjob prune-telemetry -n uipath

Kerberos authentication limitations

Kerberos-based authentication is not supported for Integration Service.

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 does not support FIPS. 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]%'

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]%'

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	Version	Release notes
Action Center	✅ New: 2.2510.3	Action Center release notes
AI Center	✅ New: 2.2510.3	AI Center release notes
AI Computer Vision	✅ New: 2.2510.3	AI Computer Vision release notes
Apps	✅ New: 2.2510.3	Apps release notes
Automation Hub	✅ New: 2.2510.3	Automation Hub release notes
Automation Ops	✅ New: 2.2510.3	Automation Ops release notes
Data Service	✅ New: 2.2510.3	Data Service release notes
Document Understanding	✅ New: 2.2510.3	Document Understanding AI Center-based projects release notes Document Understanding modern projects release notes
Insights	✅ New: 2.2510.3	Insights release notes
Integration Service	✅ New: 2.2510.3	Integration Service release notes
Orchestrator	✅ New: 2.2510.4	Orchestrator release notes
Process Mining	✅ New: 2.2510.3	Process Mining release notes
Solutions	✅ New: 2.2510.3	Solutions release notes
Test Manager	✅ New: 2.2510.3	Test Manager release notes

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component	Version
RKE2	1.36.0+rke2r1
ArgoCD	v3.3.8
gatekeeper	v3.22.2
rook	1.18.10
ceph	19.2.3
prometheus-pushgateway	v3.6.0
cert-manager	v1.20.2
kube-logging/logging-operator	6.5.1
kube-logging/config-reloader	6.5.1
istio	1.29.2
velero	1.18.0
reloader	v2.2.11
Prometheus	v3.11.3
Grafana	13.0.1
redis-operator	v8.0.18-14
redis-cluster	v8.0.18-36.14
oauth2-proxy	v7.15.2