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

Automation Suite release notes

Last updated Sep 24, 2025

2024.10.3

Release date: April 28, 2025

Support for new RHEL version

We have expanded our OS support to include RHEL 9.6. For details on the supported RHEL versions, see Compatibility Matrix.

Release date: September 24, 2025

Kerberos keytab rotation does not trigger token regeneration

Erratum - added September 24, 2025: An issue causes Kerberos keytab rotation to not immediately regenerate authentication tokens, which may lead to temporary connectivity disruptions between services and the database.

To address the issue, you must manually trigger the Kerberos ticket renewal cronjob by running the following command:

kubectl delete job tgt-rotate-manual -n uipath --ignore-not-found ; kubectl create job tgt-rotate-manual --from=cronjob/kerberos-tgt-update -n uipathkubectl delete job tgt-rotate-manual -n uipath --ignore-not-found ; kubectl create job tgt-rotate-manual --from=cronjob/kerberos-tgt-update -n uipath

We fixed the issue in Automation Suite 2024.10.5.

Orchestrator does not start when using user-assigned managed identity

Erratum - added September 24, 2025: An issue prevents the storage.useClientID parameter from being set when you select a user-assigned managed identity for object storage. As a result, Orchestrator cannot start in environments where access is restricted to user-assigned managed identities.

To address the issue, you must manually set the parameter in ArgoCD, as follows:

  1. In the ArgoCD Orchestrator application, go to Details > Parameters.
  2. In the values text box, set storage.isExternal : true and save.

We fixed the issue in Automation Suite 2024.10.5.

Temporary registry installation timeout

Erratum - added September 24, 2025: An issue causes the temporary registry installation to fail with a timeout error when connecting to registry-1.docker.io. To address the issue, refer to the Troubleshooting section.

We fixed the issue in Automation Suite 2024.10.5.

Thanos compactor stops on corrupted blocks

Erratum - added September 24, 2025: An issue causes the Thanos compactor to stop compacting metrics when it encounters corrupted blocks in the object store. This prevents compaction and leads to increased storage usage.

To address the issue, refer to the Troubleshooting section.

We fixed the issue in Automation Suite 2024.10.5.

Generating the configuration file using a GUI-based wizard

Navigating through the intricacies of a platform configuration, involving multiple flags and parameters, can at times be a challenging experience. To simplify this, we bring you the Automation Suite Installer Wizard, a new method for generating the Automation Suite cluster_config.json configuration file.
This GUI-centric tool guides you through the key configuration steps, prompting you to provide details about your Automation Suite installation. It requires details such as the targeted platform, environment type, storage needs, SQL database specifics, and more, subsequently generating the cluster_config.json file for you.

PostgreSQL for Process Mining Airflow database

For Process Mining on Automation Suite 2024.10.3, you can now choose to use PostgreSQL for the AutomationSuite_Airflow database. If you choose not to use PostgreSQL and keep using Microsoft SQLServer, Process Mining on Automation Suite 2024.10.3 will run with a legacy version of Airflow.
Refer to SQL Requirements for Process Mining for more information on how to set up a PostgreSQL AutomationSuite_Airflow metadatabase.
Important:

You are recommended to move to PostgreSQL for the Airflow database, as PostgreSQL runs with the latest versions of Apache Airflow. Latest versions of Apache Airflow have various functionality, performance, and security fixes that older versions lack.

Removed Dapr dependency for Process Mining

Starting with Automation Suite 2024.10.3, Process Mining will no longer have a dependency on Dapr.

Task-Mining, however, will still continue to have a dependency on Dapr.

If you are installing Automation Suite where Process Mining is enabled and Task Mining is not enabled, then the Dapr application will not be installed.

In case of an Automation Suite upgrade where Process Mining is enabled and Task Mining is not enabled, then the Dapr application will be automatically uninstalled.

Additional custom CA certificate support

You can include any additional custom CA certificate by providing the additonal_ca_certs key with the external CA certificate path in the cluster_config.json file.

Enhanced telemetry

Enhanced Automation Suite with a high-level summarized usage telemetry feature, provided guidance on viewing the generated XML file, and added telemetry sharing with UiPath Support via the Customer Portal.

Istio HSTS enabled by default

To enhance security, Istio HSTS is now enabled by default.

uipathctl improvements

  • You can now list all the available options for the included and excluded flags when running the prerequisite checks command. For more details about --list-options, refer to the uipathctl reference guide.
  • For better eficiency, the diagnostic checks are no longer executed during the bundle creation process. Previously, a health check was performed by default during the support bundle creation, requiring the explicit use of the --skip-diagnose flag to bypass it. For more details on how to run the diagnostic checks, refer to the uipathctl reference guide.

Bug fixes

  • Resolved an issue where proxy and Kerberos-based pipelines were not functioning correctly in Automation Suite 2024.10.0, 2024.10.1, and 2024.10.2. This issue has been fixed, restoring proper support for proxy and Kerberos authentication in pipelines.
  • An issue related to Velero migration caused the Automation Suite in-place upgrade to 2024.10.1 and 2024.10.2 to fail when the backup was enabled. We have fixed the issue.
  • An issue was causing the 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, to not work for specific nodes such as GPU, task-mining, or as-robot. We have fixed the issue.
  • Previously, the configuration of user authentication and SQL authentication for the Automation Suite cluster was interconnected. To use either of them, you had to set both kerberos_auth_config.enabled and kerberos_auth_config.enable_integrated_sql_auth parameters to true. Currently, we allow independent configuration of only user authentication by setting kerberos_auth_config.enabled to true and kerberos_auth_config.enable_integrated_sql_auth to false. Independent SQL authentication is still not supported.
  • We have fixed an issue causing the side-by-side and the in-place upgrade of Automation Suite 2022.10 or earlier to Automation Suite 2024.10.0 or later to fail when Apps was enabled and you used Kerberos authentication for the SQL Server database.
  • An issue was preventing the registry cleanup command from effectively clearing the unused Docker images from all registry pods. We have fixed the issue.
  • We have fixed an issue that blocked the Automation Suite upgrade on a backup-restored cluster.
  • We have resolved an issue causing the health check command to fail in offline environments. The issue occurred due to the incorrect parsing of Istio image versions from registries containing two or more semicolons.
  • We have fixed an issue that was causing Studio Web to throw a 404 error when using a proxy environment.

Known issues

Registry certificates not fully updated in offline scenarios

Erratum - added September 24, 2025: An issue causes the uipathctl config tls-certificates command to update only the internal certificate, while missing the certificate required by Argo CD to trust the in-cluster registry in offline scenarios.

To address the issue, you must run the following command to explicitly update the ArgoCD registry certificate in internal–external registry scenarios: 

./bin/uipathctl config argocd ca-certificates update --cacert [PATH]./bin/uipathctl config argocd ca-certificates update --cacert [PATH]

We fixed the issue in Automation Suite 2024.10.5.

GPU enablement fails with external registries containing project names

Erratum - added September 24, 2025: An issue prevents GPU enablement after adding a GPU node when using external registries with project names (such as Harbor). The required pods do not start and display an ImagePullBackoff error.

If you are using an external registry with a project name, update the NVIDIA device plugin daemonset with the following command:

# Replace REGISTRY_WITH_PROJECT_NAME with the correct value (Eg. my.registry.io:443/myproject)
# Replcae TAG with the correct value. You can get this from the <installer_directory>/versions/docker-images.json file (Eg. v0.17.1)
kubectl set image daemonset/nvidia-device-plugin-daemonset \
  -n kube-system \
  nvidia-device-plugin-ctr=<REGISTRY_WITH_PROJECT_NAME>/k8s-device-plugin:<TAG># Replace REGISTRY_WITH_PROJECT_NAME with the correct value (Eg. my.registry.io:443/myproject)
# Replcae TAG with the correct value. You can get this from the <installer_directory>/versions/docker-images.json file (Eg. v0.17.1)
kubectl set image daemonset/nvidia-device-plugin-daemonset \
  -n kube-system \
  nvidia-device-plugin-ctr=<REGISTRY_WITH_PROJECT_NAME>/k8s-device-plugin:<TAG>

We fixed the issue in Automation Suite 2024.10.5.

Orchestrator does not start when using user-assigned managed identity

Erratum - added September 24, 2025: An issue prevents the storage.useClientID parameter from being set when you select a user-assigned managed identity for object storage. As a result, Orchestrator cannot start in environments where access is restricted to user-assigned managed identities.

To address the issue, you must manually set the parameter in ArgoCD, as follows:

  1. In the ArgoCD Orchestrator application, go to Details > Parameters.
  2. In the values text box, set storage.isExternal : true and save.

We fixed the issue in Automation Suite 2024.10.5.

Task Mining Kerberos initialization failure

Erratum - added June 26, 2025: An issue causes the Task Mining service to fail to initialize in Kerberos environments. This issue occurs when the kerberos-discoverygroup-user-keytab secret is missing or when the discoverygroup app is not included in the enabledApps parameter of the IntegratedAuth app.

To address the issue, refer to the Troubleshooting section.

We fixed the issue in Automation Suite 2024.10.4.

Agent node addition failure in offline environments

Erratum - added June 26, 2025: An issue causes the addition process of agent nodes in offline environments to fail. Agent node additions require the temporary registry to be running. To address the issue, you must re-enable the temporary registry to successfully join the agent node.

We fixed the issue in Automation Suite 2024.10.4.

Frequent restarts in uipath namespace due to secret mismatch

Erratum - added June 26, 2025: An issue causes frequent restarts of deployments in the uipath namespace due to inconsistent istio-ingressgateway-certs secrets between the istio-system and docker-registry namespaces.

To address the issue, refer to the Troubleshooting section.

We fixed the issue in Automation Suite 2024.10.4.

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.

Installation fails due to CA certificates with large policy OIDs

Erratum - added June 26, 2025: An issue causes the Automation Suite installation to fail when using Certificate Authority (CA) certificates that include a CertificatePolicies section with policy OID values exceeding 4 bytes. This issue prevents Automation Suite from recognizing these CA certificates, interrupting the installation process.
To address the issue, you must either ensure that the policy OID values within the CertificatePolicies section do not exceed 4 bytes, or avoid using CA generators that add the CertificatePolicies section to the certificates.

We fixed the issue in Automation Suite 2024.10.4.

Process Mining portal fails to load

Erratum - added June 26, 2025: After upgrading from Process Mining in Automation Suite 2024.10.2 to 2024.10.3, the Process Mining portal may fail to load the process apps. An HTTP Error (400) error message is displayed when attemptimg to access the Process Mining portal.

The issue can occur when VersionSetJson is set to
{
    "Main": "6.13.0", 
    "Extra": ["6.17.0"]
}{
    "Main": "6.13.0", 
    "Extra": ["6.17.0"]
}
in the DetailsJson in the Process Mining AutomationSuite_ProcessMining_Metadata database, which breaks JSON serialization for the SemVersion object.
To solve the issue, execute the query that replaces "Extra": ["6.17.0"] with "Extra": [] in DetailsJson field in Ingestions table.
Important: You need to have write access to the Process Mining AutomationSuite_ProcessMining_Metadata production database.
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 cluster_config.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 cluster_config.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
      }
    }
  }
}
  2. After applying this configuration, you must reinstall your Automation Suite deployment to ensure the change takes effect:
    ./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --versions ./versions/helm-charts.json./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --versions ./versions/helm-charts.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.

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.3Action Center 2024.10.3
Task Mining 2024.10.3AI Computer Vision 2024.10.3Insights 2024.10.4Apps 2024.10.3
Orchestrator 2024.10.5 
  Test Manager 2024.10.3 
    

Internal third-party component versions

This Automation Suite release bundles the following internal components:

Component

Version

RKE2

1.31.4+rke2r1

ArgoCD

v2.14.4

gatekeeper

3.18.2

rook

1.16.1

ceph

19.2.0

prometheus-pushgateway

v3.0.0

cert-manager

v1.17.1

kube-logging/logging-operator

5.2.0

kube-logging/config-reloader

v0.0.7

istio

1.25.0

velero

1.15.2

reloader

v2.0.0

Prometheus

v3.2.1

Grafana

11.5.2

redis-operator

v7.8.4-9

redis-cluster

v7.8.4-95.focal

oauth2-proxy

v7.8.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.

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.