- Automation Suite on Linux Release Notes
- Automation Suite on EKS/AKS Release Notes
- Automation Suite on OpenShift release notes
2.2510.1
2.2510.1 release notes for Automation Suite on OpenShift.
Release date: December 19, 2025
Support for OpenShift Service Mesh 3.0
Automation Suite now supports OpenShift Service Mesh (OSSM) 3.0.
For installation instructions, refer to Installing and configuring the service mesh.
For the compatibility matrix between OpenShift Service Mesh versions and Automation Suite on OpenShift versions, refer to the OpenShift third-party component compatibility matrix.
Support for disabling priority class creation
You can now disable priority class creation during deployment. This capability is intended for shared cluster environments where priority classes are not required. To enable it, you must edit the input.json configuration file.
For details, refer to Creating a priority class.
Bug fixes
- Erratum - added February 9, 2026: We fixed an issue where some Document Understanding microservices failed to start, particularly in IPv4-only environments.
- We have fixed an issue that caused the prerequisite checks to fail when Process Mining was enabled. The issue occurred due to the checks incorrectly treating
cert-manageras a required component, even though it is no longer needed for Process Mining. - This release includes the fixes delivered in Automation Suite 2.2510.0+patch1.
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"}}'
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 on OpenShift 2.2510.4.
Document Understanding CPU inference setting lost when upgrading to 2.2510.2 or later
Erratum - added September 10, 2026: If you enabled CPU inference for Document Understanding modern projects (enable_cpu_inference), the setting is not carried over when you upgrade to 2.2510.2 or later. This issue occurs due to a change in the expected location of the enable_cpu_inference parameter in input.json, starting with Automation Suite 2.2510.2.
Before upgrading to Automation Suite 2.2510.2 or later, move the enable_cpu_inference parameter from the documentunderstanding root to the modernProjects section:
// Before
"documentunderstanding": {
"enable_cpu_inference": false,
"modernProjects": {
"enabled": true
}
}
// Before
"documentunderstanding": {
"enable_cpu_inference": false,
"modernProjects": {
"enabled": true
}
}
// After (2.2510.2 or later)
"documentunderstanding": {
"modernProjects": {
"enabled": true,
"enable_cpu_inference": false
}
}
// After (2.2510.2 or later)
"documentunderstanding": {
"modernProjects": {
"enabled": true,
"enable_cpu_inference": false
}
}
Studio Desktop cannot load Integration Service connectors and activities
Erratum - added July 23, 2026: In Studio Desktop, the Activities panel does not list Integration Service connectors and activities. The issue is caused by a routing misconfiguration in the intsvcs-periodic VirtualService.
To address the issue, refer to Studio Desktop cannot load Integration Service connectors and activities.
We fixed the issue in Automation Suite on OpenShift 2.2510.3.
Prerequisite checks fail when Document Understanding modern projects is enabled and AI Center is disabled
Erratum - added July 23, 2026: An issue causes the prerequisite checks command to incorrectly fail when Document Understanding modern projects is enabled and AI Center is disabled.
To address the issue, refer to Troubleshooting.
This issue is fixed in Automation Suite 2.2510.3.
AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
Erratum - added April 15, 2026: When database TLS certificate verification is enabled, some AI Center and Document Understanding pods may get stuck in Init:CrashLoopBackOff. The await-migration-completion init container fails to connect to the database, with TLS/SSL handshake errors in the logs.
To address the issue, refer to AI Center and Document Understanding pods fail to start with TLS certificate verification enabled.
We fixed the issue in Automation Suite on OpenShift 2.2510.2.
Residual istio-validation-deployment after prerequisite or health checks
Erratum - added April 15, 2026: After running the prerequisite checks (uipathctl prereq) or the health check (uipathctl health check), the istio-validation-deployment deployment created during virtual service validation may not be automatically deleted, consuming unnecessary cluster resources.
To check for residual resources in the UiPath namespace, run the following commands:
kubectl get deployments -n <uipath-namespace> | grep istio-validation-deployment
kubectl get jobs -n <uipath-namespace> | grep istio-validation-deployment
kubectl get deployments -n <uipath-namespace> | grep istio-validation-deployment
kubectl get jobs -n <uipath-namespace> | grep istio-validation-deployment
If any residual resources are present, delete them by running the following commands:
kubectl delete job -n <uipath-namespace> <istio-validation-job-name>
kubectl delete deployment -n <uipath-namespace> <istio-validation-deployment-name>
kubectl delete job -n <uipath-namespace> <istio-validation-job-name>
kubectl delete deployment -n <uipath-namespace> <istio-validation-deployment-name>
We fixed the issue in Automation Suite on OpenShift 2.2510.2.
Custom platform database name not supported when installing Process Mining
Erratum - added March 26, 2026: When Process Mining is enabled, using a custom platform database name causes the OMS backfill job to fail.
As a workaround, use AutomationSuite_Platform as the platform database name when installing Process Mining.
This issue will be fixed in Automation Suite 2.2510.2.
FIPS 140-2 support limitations
Erratum - added January 22, 2026: Insights and Integration Service are 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 these services.
For details, refer to Security and compliance.
Custom database names not supported for Solutions
Erratum - added April 15, 2026: An issue prevents you from using a custom database name for Solutions. If you specify a custom database name, the prerequisite checks fail.
To address this issue, you must use AutomationSuite_AutomationSolutions as the Solutions database name.
This issue is fixed in Automation Suite 2.2510.2.
Kerberos authentication limitations
Kerberos-based authentication is currently not supported for the following products:
- Integration Service
- Autopilot for Everyone
- AI Trust Layer (LLM Gateway, LLM Observability, Context Grounding)
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.
Context Grounding ingestion fails in offline environments
Erratum - added September 10, 2026: In offline (air-gapped) deployments, Context Grounding document ingestion fails for every file type. The reported error incorrectly indicates a problem with the file contents.
We fixed the issue in Automation Suite on OpenShift 2.2510.4.
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.1.
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.1 | Action Center release notes |
| AI Center | ✅ New: 2.2510.1 | AI Center release notes |
| AI Computer Vision | ✅ New: 2.2510.1 | AI Computer Vision release notes |
| Apps | ✅ New: 2.2510.1 | Apps release notes |
| Automation Hub | ✅ New: 2.2510.1 | Automation Hub release notes |
| Automation Ops | ✅ New: 2.2510.1 | Automation Ops release notes |
| Autopilot for Everyone | ✅ New: 2025.9.4 | Autopilot for Everyone release notes |
| Data Service | ✅ New: 2.2510.1 | Data Service release notes |
| Document Understanding | ✅ New: 2.2510.1 | Document Understanding AI Center-based projects release notes Document Understanding modern projects release notes |
| Insights | ✅ New: 2.2510.1 | Insights release notes |
| Integration Service | ✅ New: 2.2510.1 | Integration Service release notes |
| Solutions | ✅ New: 2.2510.1 | Solutions release notes |
| Orchestrator | ✅ New: 2.2510.1 | Orchestrator release notes |
| Process Mining | ✅ New: 2.2510.1 | Process Mining release notes |
| Studio Web | ✅ New: 2.2510.1 | Studio Web release notes |
| Test Manager | ✅ New: 2.2510.1 | Test Manager release notes |
- Support for OpenShift Service Mesh 3.0
- Support for disabling priority class creation
- Bug fixes
- Known issues
- Horizontal Pod Autoscaler and ArgoCD scaling conflict in HA environments
- Document Understanding CPU inference setting lost when upgrading to 2.2510.2 or later
- Studio Desktop cannot load Integration Service connectors and activities
- Prerequisite checks fail when Document Understanding modern projects is enabled and AI Center is disabled
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Residual istio-validation-deployment after prerequisite or health checks
- Custom platform database name not supported when installing Process Mining
- FIPS 140-2 support limitations
- Custom database names not supported for Solutions
- Kerberos authentication limitations
- Context Grounding ingestion fails in offline environments
- Deprecation timeline
- Bundling details
- Product versions