2024.10.4

Release date: June 26, 2025

Disaster Recovery - Active/Passive deployments

We are happy to announce that Disaster Recovery in Active/Passive configuration is now supported for Automation Suite on OpenShift.

Now you can configure Automation Suite in a way that can withstand the complete failure of nodes, entire data centers, or even regions.

Automation Suite deployments in Active/Passive mode support the following scenarios:

• Same-region deployment
• Cross-region deployment

For details, see Disaster Recovery - Active/Passive and Quick links.

Changes to the patching procedure

The procedure for applying patches now includes an additional step that requires you to download and use the corresponding uipathctl patch version before proceeding with the patch.

For more details, refer to Applying a patch.

Changes to OpenShift version support

We have expanded our compatibility to include OpenShift version 4.17. Additionally, we have removed OpenShift version 4.13 from the list of compatible versions.

If you move from an older Automation Suite version, make sure you use a supported OpenShift version before starting the upgrade.

For more details about the supported OpenShift versions, refer to Compatibility matrix.

Bug fixes

• Log forwarding did not work in proxy setups because the proxy environment variables were not set in the logging pods. We have fixed the issue.
• Licensing SQL connection errors occurred when the Data Source property specified both a named instance and a port. We have fixed the issue.

Known issues

Prerequisite checks fail when Document Understanding modern projects is enabled and AI Center is disabled

Erratum - added July 2, 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 2024.10.9.

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.

Residual istio-validation-deployment after prerequisite or health checks

Erratum - added March 26, 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

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>

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.

Prerequisite checks fail when Process Mining is enabled

Erratum - added December 19, 2025: An issue causes the prerequisite checks to fail when Process Mining is enabled. The issue occurs due to the checks still requiring cert-manager, although cert-manager is no longer needed for Process Mining starting with Automation Suite 2024.10.3.

The failure message is a false positive and can be safely ignored.

We fixed the issue in Automation Suite 2024.10.7.

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.4	Automation Ops 2024.10.4	AI Center 2024.10.4	Action Center 2024.10.4
Process Mining 2024.10.4	AI Computer Vision 2024.10.4	Insights 2024.10.4	Apps 2024.10.4
	Document Understanding AI Center-based projects 2024.10.4 Document Understanding modern projects 2024.10.4	Orchestrator 2024.10.6
		Test Manager 2024.10.4
		Data Service 2024.10.4

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.