- Automation Suite on Linux Release Notes
- Automation Suite on EKS/AKS Release Notes
- Automation Suite on OpenShift release notes

Automation Suite release notes
2024.10.2
Release date: April 28, 2025
Full migration is now supported in Automation Suite 2024.10.2.
Compared to the full migration steps in Automation Suite 2023.10, in this version there is an additional migration step in which you can update the schema of the Insights and Orchestrator databases after previously restoring them.
UiPath.OrganizationMigrationApp
tool:
- We provide an inner exception during a database connection test for enhanced error logging and debugging.
- We improved the merging process of single sign-on users (SSO) from multiple organizations to handle database conflicts more efficiently. The update also provides accurate migration success messages and prevents potential data duplication. This enhancement significantly benefits organizations utilizing the MSI to Automation Suite setup with a multi-tenant configuration and SSO.
For more details, refer to Performing a full migration.
Release date: March 17, 2025
To simplify the migration process, you are no longer required to install .NET Core Desktop Runtime for 64-bit (x64) systems on your machine to run the Automation Cloud Migration Tool for a single tenant.
Release date: February 17, 2025
Document Understanding modern projects are now supported in Automation Suite on AKS offline deployments and Azure Government environments.
- Erratum - added February 25, 2025: We fixed an issue which caused increased infrastructure load, if misconfigured. This issue impacted users who had Integration Service enabled on Automation Suite for EKS/AKS, versions 2024.10.0 and 2024.10.1, and did not have storage queues created.
- An issue was preventing Fluentd from sending logs to remote locations due to a lack of memory buffer. We have fixed the issue.
- An issue prevented the inclusion of Insights dashboards and Studio Web data in backups. We have fixed the issue.
Erratum - added June 26, 2025: Log forwarding does not work in proxy setups because the proxy environment variables were not set in the logging pods. To address the issue, refer to the Troubleshooting section.
We fixed the issue in Automation Suite 2024.10.4.
uipath
. This issue is due to the network policy incorrectly expecting the presence of a uipath
namespace regardless of the chosen namespace.
uipath
namespace before deploying Automation Suite.
We have fixed this issue in Automation Suite 2024.10.4.
Cannot evict pod as it would violate the Pod’s disruption budget
.
intsvcs-periodic
deployment using the following command:
kubectl scale deployment intsvcs-periodic --replicas=2 -n uipath
kubectl scale deployment intsvcs-periodic --replicas=2 -n uipath
We have fixed this issue in Automation Suite 2024.10.4.
Erratum - added June 26, 2025: Licensing SQL connection errors occur when the Data Source property specified both a named instance and a port.
We fixed the issue in Automation Suite 2024.10.4.
input.json
file to disable secret rotation in the platform configuration. This change will persist through Automation Suite upgrades
and reinstalls.
Take the following steps:
- Update the
platform
section in theinput.json
file as shown in the following example:"platform": { "enabled": true, "advanced_configuration": { "identity-service": { "secretRotation": { "enabled": false } } } }
"platform": { "enabled": true, "advanced_configuration": { "identity-service": { "secretRotation": { "enabled": false } } } } - After applying this configuration, you must reinstall your Automation Suite deployment to ensure the change takes effect:
uipathctl manifest apply input.json --versions versions.json
uipathctl manifest apply input.json --versions versions.json
Erratum - added May 14, 2025: An issue causes service disruptions due to the automatic secret rotation, making services temporarily inaccessible.
To address this issue, take the following steps:
- Restart the affected service to restore its normal functionality.
- Navigate to the ArgoCD UI and from the platform applicatio, select Details > Parameters. Edit the values to add
"secretRotation: enabled: false"
underidentity-service
. You must take this step after each Automation Suite upgrade or reinstallation.
For AI Center, all skills must be stopped and started from AI Center UI.
intsvcs/oauth-token-refresh
configured at the service level,
the OAuth token refresh job is attempting to fetch a version that is not available
in the UiPath offline registry. This causes issues during execution.
We have fixed this issue in Automation Suite 2024.10.3.
Erratum - added February 27, 2025: For this version of Automation Suite, you need to use SQL Server version 2019 or higher for proper operation of Orchestrator and AI Center.
You cannot currently perform a full migration from standalone products version 2024.10 to Automation Suite 2024.10 using the UiPath.OrganizationMigrationApp tool. We are actively working on introducing support for this scenario.
In the meantime, you can perform a single-tenant migration. For details on this migration option, refer to Single tenant migration.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
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.
DISCOVER | BUILD | MANAGE | ENGAGE |
---|---|---|---|
Automation Ops 2024.10.1 | AI Center 2024.10.2 | Action Center 2024.10.2 | |
Task Mining 2024.10.2 | AI Computer Vision 2024.10.2 | Insights 2024.10.2 | Apps 2024.10.2 |
Orchestrator 2024.10.3 | |||
Test Manager 2024.10.2 | |||
This Automation Suite release bundles the following internal components:
For the Kubernetes versions that each Automation Suite version supports, see Kubernetes compatibility.
Component |
Version |
---|---|
Istio |
1.23.0 |
ArgoCD |
2.13.3 |
Prometheus |
3.1.0 |
Grafana |
11.4.0 |
Fluentd and Fluent-bit |
logging-operator: 5.0.1 logging-operator-logging: 5.0.1 |
Gatekeeper |
3.18.2 |
Cert-Manager |
1.16.2 |
Velero |
8.3.0 |
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.
- Support for full migration
- Removed dependency for single tenant migration
- Support added for Document Understanding modern projects
- Bug fixes
- Known issues
- Log streaming does not work in proxy setups
- Deployment issue on shared EKS clusters with custom namespace
- Kubernetes upgrade failure
- Licensing SQL connection error
- Service disruptions due to automatic secret rotation
- OAuth token refresh issue due to incorrect version
- Orchestrator and AI Center require SQL Sever version 2019 and higher
- Full migration from standalone products to Automation Suite not supported
- Deprecation timeline
- Bundling details
- Product versions
- Internal third-party component versions
- Migration tool version