Automation Suite release notes

We are happy to announce the addition of Document Understanding modern projects, Integration Service, and Studio Web to our Automation Suite product portfolio. This expansion aligns with our aim to maintain parity with the functionalities offered via Automation Cloud.

If you plan to enable these new products, make sure to check out the cross-product dependencies and that you meet all the prerequisites.

All the details about the installation and configuration of these newly onboarded products are available in the Automation Suite on EKS/AKS Installation Guide. For details on how make the most out of the functionality of these products, refer to the individual product guides:

In an attempt to make your start with Automation Suite easier and cost-effective, we are now introducing the lite mode. With it, you can start with fewer infrastructure requirements and when ready, transition to high availability for specific services.

A key benefit of lite mode is its resource efficiency. It offers full functionality without the need for high availability across all services. Consequently, the lite profile needs fewer resources, a value-added feature for infra-budget-conscious organizations.

Notably, lite mode is not just for small-scale operations. This mode is designed with scalability in mind, so as your needs grow, lite mode grows with you.

Lite mode is versatile, accommodating a wide array of scenarios, such as the following:

To provide you with a wider range of deployment options and increase the flexibility of our offering, we are happy to announce that you can now deploy Automation Suite to a shared cluster, alongside your other software deployments. Deploying to a shared cluster comes as an alternative to the existing scenario of deploying Automation Suite to a dedicated cluster.

We have added Bottlerocket to the list of operating systems supported by Automation Suite on EKS. For more details, see Kubernetes cluster and nodes.

You can now avoid managing credentials by enabling AKS pods to use a Kubernetes identity, such as a service account. Workload identity also allows Kubernetes applications to access Azure resources securely with Microsoft Entra ID, based on annotated service accounts.

To learn more about workload identity, see Workload identity configuration.

For details on the limitations of the feature, see Known issues.

We now support Transport Layer Security (TLS) 1.3. This new TLS version brings several key improvements, being more secure than its predecessor, TLS 1.2, and offering speedier connections and improved performance.

If you must comply with the Federal Information Processing Standard 140-2 (FIPS 140-2), we have good news for you. It is now possible to enable FIPS 140-2 on machines on which you plan to perform a new Automation Suite on EKS installation.

For more information on FIPS 140-2, see Security and compliance.

For details on the limitations of the feature, see Known issues.

Erratum - added January 27, 2025: Automation Suite on EKS now supports Amazon Linux 2023 (AL2023).

You can now install Automation Suite on nodes on which you enabled FIPS using the Amazon Linux 2023 (AL2023) image. This update aligns with the transition that Amazon made from AL2 to AL2023.

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

Despite the wizard offering an easier way to create a configuration file, some complex configuration scenarios might not yet be covered as the tool is currently in public preview. We eagerly invite you to experiment with this tool and kindly share your feedback to help us improve this feature.

For details, see Generating the configuration file using a wizard.

We are excited to announce that you can now update the Fully Qualified Domain Name (FQDN) of your Automation Suite cluster.

For details about the FQDN update procedure, see Configuring the FQDN post-installation.

Automation Suite now uses AWS Signature Version 4 for all S3 API requests. This impacts the use of Automation Suite with S3 servers that do not support AWS Signature Version 4.

Automation Suite now supports server-side encryption with Key Management Service (SSE-KMS) on AWS S3 buckets.

For more information on SSE-KMS, see the AWS documentation.

We are happy to announce that Automation Suite now supports Harbor and other external registries that require you to create a project before pushing or pulling images from the registry.

For more details, see Uploading the Automation Suite artifacts to the external OCI-compliant registry and External OCI-compliant registry configuration.

To take full advantage of the features that Apps offers, you now must provide a unique subdomain with a Fully Qualified Domain Name (FQDN). You must make the following changes:

Automation Suite 2024.10 introduces automatic identity token-signing certificate rotation. This feature automates the lifecycle of your signing keys, offering enhanced security and reducing the need for manual certificate management.

If you're deploying Automation Suite 2024.10 for the first time, this feature is enabled by default. The option for manual management of signing certificates remains available, and those who prefer manual control or have specific operational requirements can disable automatic certificate rotation.

For users upgrading to 2024.10 from an older version, automatic management is disabled by default but can be enabled if desired.

For details on how to enable or disable automatic certificate rotation, see Automatic certificate rotation in the Automation Suite on Linux documentation, or Automatic certificate rotation in the Automation Suite on AKS/EKS documentation.

We are excited to introduce personal access tokens (PATs). PATs provide developers with an efficient and secure method to obtain tokens with user-scoped access. PATs can limit risk when working with applications or automations that do not allow for other authentication mechanisms, or where you do not want to provide your credentials. If the app is compromised, you simply revoke the PAT.

The core capabilities:

For detailed information on implementing PATs, please refer to the docs on personal access tokens.

Personal access tokens (PATs) can be managed by organization administrators. PATs can limit risk when working with applications or automations that do not allow for other authentication mechanisms, or where you do not want to provide your credentials. If the app is compromised, you simply revoke the PAT.

Organization administrators can manage issued PATs, enabling easy revocation of access when necessary.

For detailed information on managing PATs, please refer to Managing PATs.

For more details about prerequisites check, see Prerequisite checks.

We're happy to announce various fixes and improvements that ensure an even more accurate estimate of the hardware requirements for any Automation Suite deployment. The tool now takes into account the additional data disk required by Document Understanding and AI Center. Also, it now takes a single click to share the UiPath Automation Suite Install Sizing Calculator URL along with your currently selected configuration.

If you want to take the UiPath Automation Suite Install Sizing Calculator for a spin, see Capacity planning.

We've rolled out some significant updates geared towards improving SAML SSO. Here's a quick overview of what's new:

We have introduced a high contrast theme that ensures enhanced contrast for a set of UI elements.

For more information, refer to Selecting the theme.

You can now manage the visibility of three new services in the left navigation bar, in order to customize the UI for each user:

For more information, see the Hide unused services documentation.

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.

We have fixed this issue in Automation Suite 2024.10.4.

We have fixed this issue in Automation Suite 2024.10.4.

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.

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:

For AI Center, all skills must be stopped and started from AI Center UI.

Erratum - added April 2, 2025: An issue is preventing the inclusion of Insights dashboards and Studio Web data in backups. To address this issue, refer to the Backing up the cluster page. The issue is fixed in Automation Suite 2024.10.2.

Erratum - added February 27, 2025: For this version of Automation Suite, you need to use SQL Server version 2019 or higher for proper operation of Orchestrator and AI Center.

Erratum - added February 17, 2025: An issue prevents Fluentd from sending logs to remote locations due to a lack of memory buffer. To address this issue, you must add a memory limit for Fluentd to prevent disruptions or delays when transmitting logs to a remote location.

This issue is fixed in Automation Suite 2024.10.2.

Erratum - added January 20, 2025: Insights, Studio Web, and Task Mining do not currently support Microsoft Entra ID (formerly Azure Active Directory) authentication configuration for access to SQL, storage, and other resources that support Microsoft Entra.

Erratum - added December 18, 2024: Using an SQL Server version prior to 2019 causes an Automation Suite installation issue due to the Resource Catalog service not supporting SQL Server versions prior to 2019. We fixed the issue in Automation Suite 2024.10.1.

When you migrate from Automation Suite on Linux to Automation Suite on EKS/AKS, Insights-related volumes are occasionally created in two different zones. As a result, you may encounter problems when bringing up the Insights service. To address the problem, see Troubleshooting.

We fixed the issue in Automation Suite 2024.10.1.

Erratum - added December 18, 2024: Following an upgrade to Automation Suite 2024.10, you cannot access Automation Hub due to database schema discrepancies. To address the problem, see Troubleshooting.

We fixed the issue in Automation Suite 2024.10.1.

Erratum - added December 18, 2024: An issue causes upgrades to fail when the existing Insights PVC sizes are inadvertently overridden. To address this problem, you must manually change the PVC sizes in ArgoCD UI. For details, see the Troubleshooting section.

We fixed this issue in Automation Suite 2024.10.1.

Erratum - added December 18, 2024 We have identified an issue with the backup logic in Automation Suite for AKS/EKS. Specifically, this defect excludes the backup of Insights dashboards. However, all historical data is successfully backed up.

We are working diligently to resolve this issue. We aim to develop and implement a mitigation approach as early as possible.

If you are using Automation Suite on AKS/EKS along with UiPath Insights, this defect may affect your operations. While we address this issue, we suggest manually exporting your dashboards as a preventive measure.

Note that backups are mainly used as a recovery method in the event of a disaster-level incident or in preparation for an Automation Suite upgrade. This is particularly useful if an upgrade fails and stored data needs to be restored to its previous state.

You cannot currently perform a full migration from standalone products version 2024.10 to Automation Suite 2024.10 using the UiPath.OrganizationMigrationApp tool. We are actively working on introducing support for this scenario.

In the meantime, you can perform a single-tenant migration. For details on this migration option, refer to Single tenant migration.

In this release, Document Understanding modern projects are not supported in Automation Suite offline deployments and Azure Government environments.

Generative AI features, including Generative Annotation and Generative Extraction, are not currently available in Document Understanding in Automation Suite.

If Document Understanding is enabled on your tenant without the activation of Document Understanding modern projects, the Document Understanding application (accessible from the list on the left side) will not work.

For more information, refer to the Document Understanding Release Notes guide.

Studio Web, Insights, and Task Mining do not support workload identity. If you enable workload identity, you must disable these products.

Studio Web, Insights, and Integration Service are not supported on FIPS 140-2. If you install Automation Suite on FIPS 140-2-enabled machines, you must disable these products.

Forwarding infrastructure logs to Splunk is currently not possible in Automation Suite 2024.10 because the Splunk Connect plugin for Kubernetes is no longer supported. The OpenTelemetry Collector, which you can use to gather logs, is also not supported in this Automation Suite version.

For more information on managing external tools, refer to Responsibility matrix.

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.

This Automation Suite release bundles the following internal components:

For the Kubernetes versions that each Automation Suite version supports, see Kubernetes compatibility.

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.