automation-suite
2024.10
true
  • Automation Suite on Linux Release Notes
    • 2024.10.0
    • 2024.10.1
    • 2024.10.4
  • Automation Suite on EKS/AKS Release Notes
  • Automation Suite on OpenShift release notes
    • 2024.10.0
    • 2024.10.1
    • 2024.10.4
UiPath logo, featuring letters U and I in white

Automation Suite release notes

Last updated Jul 17, 2025

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

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

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

CORS configuration issue with ODF buckets

Erratum - added July 14, 2025: An issue causes Document Understanding and AI Center labeling tasks in Action Center to fail when OpenShift Data Foundation (ODF) is used as the objectstore. This occurs due to limitations in configuring CORS policies on ODF buckets, which affects the use of presigned URLs required for loading labeling tasks.

To address the issue, you must set the following flag in your input.json file for each product that interacts with the objectstore:
"disablePresignedUrl": true"disablePresignedUrl": true

Setting this flag ensures compatibility with ODF by disabling presigned URL usage and allowing labeling tasks to load correctly.

For more details, refer to Configuring OpenShift Data Foundation.

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.

DISCOVERBUILDMANAGEENGAGE
AI Center 2024.10.4Action Center 2024.10.4
AI Computer Vision 2024.10.4Insights 2024.10.5Apps 2024.10.4
  Orchestrator 2024.10.6 
  Test Manager 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.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo
Trust and Security
© 2005-2025 UiPath. All rights reserved.