2024.10.2

Release date: 17 February 2025

Support for full migration

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.

Also, we implemented the following improvements in the 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

Removed dependency for single tenant migration

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

Upgrading Automation Suite

Erratum - added February 25, 2024: You can now upgrade Automation Suite on OpenShift. For detailed instructions, refer to the Upgrading Automation Suite page.

Support for OpenShift Redis Community Operator

We have introduced support for OpenShift Redis Community Operator by OpsTree Solutions. However, we recommend the use of OpenShift Redis Enterprise Operator.

For details on the OpenShift Redis Community Operator supported versions, see Compatibility matrix.

Bug fixes

• Erratum - added June 26, 2025: We have fixed an issue where Automation Suite installations failed due to Certificate Authority (CA) certificates not being recognized. The issue occurred when the CertificatePolicies section included policy OID values exceeding 4 bytes.

Known issues

FIPS 140-2 support limitations

Erratum - added January 22, 2026: 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.

For details, refer to Security and compliance.

Log streaming does not work in proxy setups

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.

Licensing SQL connection error

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.

Service disruptions due to automatic secret rotation

Erratum - added June 26, 2025: To address this issue, you can edit the 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:

1. Update the platform section in the input.json file as shown in the following example:

   "platform": {
     "enabled": true,
     "advanced_configuration": {
       "identity-service": {
         "secretRotation": {
           "enabled": false
         }
       }
     }
   }
   

2. 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
   

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:

1. Restart the affected service to restore its normal functionality.
2. Navigate to the ArgoCD UI and from the platform applicatio, select Details > Parameters. Edit the values to add "secretRotation: enabled: false" under identity-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.

Orchestrator and AI Center require SQL Sever version 2019 and higher

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.

Full migration from standalone products to Automation Suite not supported

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.

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

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 Hub 2024.10.2	Automation Ops 2024.10.1	AI Center 2024.10.2	Action Center 2024.10.2
Process Mining 2024.10.2	AI Computer Vision 2024.10.2	Insights 2024.10.2	Apps 2024.10.2
	Document Understanding AI Center-based projects 2024.10.2 Document Understanding modern projects 2024.10.2	Orchestrator 2024.10.3
		Test Manager 2024.10.2
		Data Service 2024.10.2

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.