Automation Suite release notes
Release date: December 18, 2024
READ_COMMITTED_SNAPSHOT option is enabled in the SQL Server database. We have implemented this check validation for Orchestrator, Apps, and Process
Mining.
For more on prerequisites checks, see Validating the prerequisites.
-
The support bundle now collects logs for the
uipath-authandveleronamespaces. -
The support bundle now captures custom resources.
We continue to provide security updates and patches to address Common Vulnerabilities and Exposures (CVEs).
- Erratum - added June 10, 2025:
In multi-node (HA) setups where Grafana is deployed with two replicas, a lack of
common data sources between the replicas caused issues in user session management.
This resulted in errors such as
Dashboard not foundandInvalid dashboard UID in the requestappearing in the Grafana dashboard. We have fixed this issue. -
We have fixed an Insights annotation issue that would block the Automation Suite installer.
-
We have fixed an issue that caused RKE2 log collection to run indefinitely for some system commands.
-
We have fixed an issue causing unnecessary DNS resolution validation for
redis.<primary-fqdn>andredis-db.<primary-fqdn>during Active/Passive prerequisite checks. This behavior no longer occurs. -
We have fixed an issue that occurred in non-HA Redis scenarios, where the
redis-cluster-0pod could get stuck in a terminating state during node drain operations. This behavior no longer occurs. -
When using style attributes in the HTML tags while customizing your Login page, they reflected accurately in the preview. However, upon saving the changes, the style attributes were deleted automatically. Now, all style attributes used within tags persist after saving your changes.
-
We fixed a bug that was breaking SAML2 when basic authentication was disabled, along with various other bugs.
Orchestrator database validation issue
sql.create_db parameter is set to true in cluster_config.json.
/opt/UiPathAutomationSuite/UiPath_Installer/Prerequisite_Checks/sql/scripts/validation.json and set advancedDbConfig.connectionStringParameter to "", under "service": "orchestrator", as shown in the following example:
"advancedDbConfig": [{
"dbName": "AutomationSuite_Orchestrator_test",
"connectionStringParameter": "",
"optionalCommands":["ALTER DATABASE AutomationSuite_Orchestrator SET READ_COMMITTED_SNAPSHOT ON;"]
}]"advancedDbConfig": [{
"dbName": "AutomationSuite_Orchestrator_test",
"connectionStringParameter": "",
"optionalCommands":["ALTER DATABASE AutomationSuite_Orchestrator SET READ_COMMITTED_SNAPSHOT ON;"]
}]We fixed the issue in Automation Suite 2023.4.12.
Kube-proxy health check not working
node-monitor component, which monitors the node for issues such as checking kube-proxy health or if ip_forward is enabled, and cordons the node if issues arise, is not working for specific nodes such as GPU, task-mining, or as-robot. We have fixed this issue in Automation Suite 2023.4.12.
Email alerts configuration failure post upgrade
Erratum - added February 13, 2025: An issue affects the functionality of email alerts configuration and the setup of multiple receivers after upgrading from Automation Suite 2022.10. To address this issue, see Troubleshooting.
This issue is fixed in Automation Suite 2023.4.11.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
Product versions
To find out what has changed on each Automation Suite product, visit the following links.
If the product is greyed out, this new Automation Suite version does not bring any changes to it.
Internal third-party component versions
This Automation Suite release bundles the following internal components:
|
Component |
Version |
|---|---|
|
RKE2 |
1.30.5+rke2r1 |
|
ArgoCD |
2.12.6 |
|
kube-logging/logging-operator |
4.9.1 |
|
config-reloader |
v0.0.5 |
|
ceph |
17.2.6 |
|
rook-ceph |
1.14.6 |
| prometheus-pushgateway |
1.10.0 |
|
cert-manager |
1.16.1 |
|
rancher-istio |
105.4.0-up1.23.2 |
| rancher-gatekeeper |
104.0.1-up3.13.0 |
| rancher-monitoring |
105.1.0-up61.3.2 |
|
longhorn |
1.6.3 |
|
longhorn-crd |
1.1.100 |
|
reloader |
1.0.95 |
|
csi-driver-smb |
1.16.0 |
|
velero |
1.14.1 |
|
redis-operator |
7.4.6-2 |
|
redis-cluster |
7.4.6-102 |
|
oauth2-proxy |
7.7.1 |
Migration tool version
The migration tool version you need depends on the standalone products you plan to migrate and the targeted Automation Suite version. For more details, see Migration compatibility matrix.
For instructions on migrating a standalone product to the current version of Automation Suite, see Full migration.
- New prerequisite check
- Support bundle enhancements
- Logging enhancement
- Security enhancements
- Bug fixes
- Known issues
- Orchestrator database validation issue
- Kube-proxy health check not working
- Email alerts configuration failure post upgrade
- Deprecation timeline
- Bundling details
- Product versions
- Internal third-party component versions
- Migration tool version