- Automation Suite on Linux Release Notes
- Automation Suite on EKS/AKS Release Notes
- Automation Suite on OpenShift release notes
Automation Suite release notes
2024.10.3
Release date: April 28, 2025
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.
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:
input.json configuration file, is now
generally available.
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.
node_labels parameter in the
input.json file.
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.
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.
AutomationSuite_Airflow metadatabase.
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.
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.
additonal_ca_certs key with the external CA certificate path in the input.json file.
-
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-diagnoseflag to bypass it. For more details on how to run the diagnostic checks, refer to the uipathctl reference guide.
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"underidentity-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.
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
argocdnamespace. -
Sync the application manually with the Replace option selected.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
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.
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.
- Deploying multiple Automation Suite instances to a single cluster
- Automation Suite Installer Wizard available in GA
- Labeling nodes to run targeted prerequisite checks
- PostgreSQL for Process Mining Airflow database
- Removed Dapr dependency for Process Mining
- Additional custom CA certificate support
- Istio HSTS enabled by default
- uipathctl improvements
- Known issues
- Service disruptions due to automatic secret rotation
- Monitoring application stuck in Progressing state
- Deprecation timeline
- Bundling details
- Product versions
- Migration tool version
