automation-suite

2024.10

true

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

Automation Suite release notes

Last updated Nov 6, 2025

2024.10.3

Release date: April 28, 2025

Deploying multiple Automation Suite instances to a single cluster

Now you have the ability to deploy multiple Automation Suite instances to a single OpenShift cluster. This improvement implies that you can now add individual input.json configuration files containing information specific to each Automation Suite instance, allowing you to have separate Automation Suite instances set up without the need for additional OpenShift clusters.

Additionally, you can now manage and monitor multiple Automation Suite installations in a single OpenShift cluster using ArgoCD. This is particularly useful, for example, for validating Automation Suite upgrades by hosting both the staging and production environments on the same cluster.

Moreover, creating an individual input.json configuration file for each installation allows you to segregate data layers effectively. This offers significant benefits if you prefer to segregate environments based on different versions, data types, and workloads within the same cluster.

To deploy multiple Automation Suite instances to a single cluster, perform these steps:

Automation Suite Installer Wizard available in GA

We are excited to announce that the Automation Suite Installer Wizard, the new method for generating the Automation Suite input.json configuration file, is now generally available.

Labeling nodes to run targeted prerequisite checks

We added back the node_labels parameter from the input.json file, thus re-adding support for prerequisite checks by node labels, which was removed in Automation Suite on OpenShift 2024.10.1.

You can now use labels to specify the nodes that you want to run prerequisite checks and workloads on, by using the new node_labels parameter in the input.json file.

To provide the value of node labels to the input.json file, you must enter the corresponding labels in key-value format, as shown in the following example:

"node_labels": {
    "node-role.kubernetes.io/worker": ""
  }  "node_labels": {
    "node-role.kubernetes.io/worker": ""
  }

For additional information on label syntax and restrictions, see the Kubernetes documentation.

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.

In case of an Automation Suite upgrade where Process Mining is enabled, then you have to explicitly uninstall Dapr post upgrade. For more details, refer to the Uninstalling Dapr section.

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 input.json file.

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.

Known issues

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:

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
      }
    }
  }
}"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.jsonuipathctl 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" 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.

Monitoring application stuck in Progressing state

After service installation, the monitoring application may remain in a Progressing state in ArgoCD.

To address this issue, you must manually sync the monitoring application with the Replace option:

In the ArgoCD UI, go to the monitoring application in the argocd namespace.
Sync the application manually with the Replace option selected.

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

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.

On this page