Automation Suite
  • Automation Suite on Linux Release Notes
    • 2023.10.0
    • 2023.10.1
    • 2023.10.2
  • Automation Suite on EKS/AKS Release Notes
Banner background image
Automation Suite Release Notes
Last updated Feb 28, 2024


Release date: November 22, 2023

New UiPath.OrganizationMigrationApp version released

We have released a new version of UiPath.OrganizationMigrationApp, the tool helping you migrate from a standalone product to Automation Suite. The new version of the tool now enables you to migrate to Automation Suite 2023.10.0.

Release date: November 3, 2023

What's new

Streamlined installation experience

We have revamped our installation experience to ensure that all installation modes, regardless of whether they are online/offline or single-node/multi-node, share similar steps and leverage the same commands. These improvements are aimed at creating a more consistent and seamless installation experience for all users.

Note that now the interactive installer serves a slightly different purpose as you can use it only to generate the cluster_config.json file, but it does not perform the actual installation.

For more details, see the following documentation:

Introducing side-by-side upgrades

You can now perform an Automation Suite upgrade using parallel clusters. This new upgrade method is called side-by-side upgrade, and it allows you to switch traffic from the old Automation Suite cluster (often referred to as the blue deployment in the industry) to the new cluster (the green deployment). One of the benefits of this approach is that your current environment is not impacted by the upgrade operation in any way. In addition to that, if you encounter issues during upgrade, you can easily roll back to the old deployment.

For extensive requirements, an upgrade matrix, and instructions, see Performing a side-by-side upgrade.

Side-by-side upgrades are the preferred method for upgrading your Automation Suite instance due to its efficiency and less risk of disruptions to workflow operations.

In-place upgrades enhancements

As an alternative to the side-by-side upgrade mechanism, you can use the in-place upgrade method to move from one Automation Suite version to another. If you have ever upgraded Automation Suite in the past, then you should be familiar with this method.

What is specific to this upgrade process is that it keeps your settings and data intact on the same hardware. There is only one cluster involved, which means that you should rely on backup and restore operations in case you want to revert to a previous state.

While this is the upgrade mechanism we have been using until now, you should know that we have considerably reduced its complexity. The in-place upgrade is now the same for both online and offline scenarios. Moreover, while previously you had to choose between an automated and a manual upgrade process, the way we designed the upgrade flow makes this distinction irrelevant. So there is one single set of instructions for all of you. As a result of this improvement, we have removed from our offering the tool, which used to help you perform an automation upgrade.

For extensive requirements, an upgrade matrix, and instructions, see Performing a in-place upgrade.

Migration from Automation Suite on Linux to Automation Suite on EKS/AKS

If you are already using Automation Suite on Linux, but you now think that Automation Suite on EKS/AKS would better cater to your needs, we have good news for you. Migrating to a new installation of Automation Suite on EKS/AKS is now possible.

Note that currently you cannot migrate from Automation Suite embedded to an existing installation of Automation Suite on EKS/AKS.

For details on the requirements, required data migration operations, and step-by-step instructions, see Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS.

Stabilization and quality enhancement through Longhorn removal

In our continuous mission to improve stability and quality, we have implemented an alternative mechanism to Longhorn. This change outlines a direct integration of data and volumes with the disk attached to server machines, leading to several implications:

  • Insights, Docker registry, and monitoring applications now exclusively run on server nodes.

  • External objectstore buckets for Insights can now be configured. For details, see External Objectstore configuration.

  • We have added support for NFSv3.

  • Once the upgrade process is completed without migrating from Longhorn, a cluster restored from a backup would not have Longhorn.

  • AI Center pipeline requires additional storage. The pipeline operates on the machine where the extra AI Center disk has been mounted, which could either be a server or agent machine.

Introducing uipathctl

As part of an initiative to unify our CLI tools, we are introducing uipathctl. Currently, the main purposes of the new tool are to help you diagnose and troubleshoot issues affecting your Automation Suite installation, perform a side-by-side upgrade, migrate from Automation Suite on Linux to Automation Suite on EKS/AKS, and migrate to an external OCI-compliant registry.
Stay tuned and watch uipathctl become the go-to tool in many other scenarios.

Objectstore access without pre-signed URLs

The latest release introduces the capability to disable access via pre-signed URLs, enhancing the authority over your external objectstore.

Please note, once this setting is enabled, it is irreversible and applies globally. Individual product-level alterations are not possible.

Take into account that this particular configuration does not support Task Mining and specific activities including Write Storage Text, Upload Storage File, List Storage Files, Read Storage Text, Download Storage File, and Delete Storage File.

Enhanced features for external Docker registry

We have made substantial enhancements to the external Docker registry. You can now benefit from these new functionalities:

  • Your external Docker registry can be equipped with its private certificate, giving you an additional layer of security.

  • In addition to the usage of a mirror registry script, which requires internet access to copy the Automation Suite artifacts, we now support the script. This script will take an offline tar bundle, unpack it, and upload its content directly to the external Docker registry, providing more flexibility and options for managing your registry.

Split offline bundle for customers with restricted network access

To better accommodate those with restrictive network access, we have introduced a split as.tar.gz file, which you can use to perform an offline installation. The offline bundle is split into 52 parts for easier downloading, and you can reassemble it once all parts are downloaded.
Please note, the option to download the full as.tar.gz file in one go continues to remain available for those with sufficient bandwidth.

For more information on how to download and merge these split files, visit our official documentation.

New RHEL version supported

You can now install Automation Suite on machines running Red Hat Enterprise Linux (RHEL) 8.8.


RHEL kernel version kernel-4.18.0-477.10.1.el8_8 is affected by an issue that interrupts the installation or management of the Automation Suite cluster. Make sure that none of the Automation Suite nodes uses this kernel version either pre- or post-installation. You can update the kernel version by running the following command:

dnf install -y kernel kernel-tools kernel-tools-libsdnf install -y kernel kernel-tools kernel-tools-libs

SELinux support

All Automation Suite versions support out-of-the-box SELinux, with default policies enabled.

IMDSv2 support

We now support IMDSv2 for connecting with the AWS S3 using the instance profile.

Deprecation of ArgoCD UI documentation

To ensure adherence to best practices and maintain the stability of your operations, we are steering away from the use of the ArgoCD UI as a means to change settings or parameters.

Instead, we are emphasizing the recommendation to use the cluster_config.json file for these purposes. This move aims to maintain a consistent source of truth for your configurations.

However, you can continue to use the ArgoCD UI to troubleshoot, see logs, or other similar operations.

Licensing news

Audit log messages change

The audit data message displayed when a user is removed by an administrator, and their licenses are consequently deallocated, has been improved for clarity. You can now expect to see this in such cases: User <administrator_name> deallocated all licenses of user(s) <user_names>.

AI Units allocation

AI units can now also be allocated at the tenant level. This is done from the license allocation window corresponding to the desired tenant in the Admin section.

License allocation endpoints

Two new endpoints are available for allocating licenses from the API:

  • GET/api​/account​/{accountId}​/user-license​/group​/{groupId} - call this endpoint to retrieve a list of all available user licenses for creating or editing a group.
  • You need View permission on License to use this endpoint.
  • PUT/api/account/{accountId}/user-license/group/{groupId} - call this endpoint to allocate or update a group rule.
  • You need Write permission on License to use this endpoint.

Introducing the Citizen Developers user group

We're excited to announce the latest enhancement to our platform's access control capabilities — the introduction of a new user group: Citizen Developers. This new group is defined at the organization level and will be seamlessly integrated across all services within the platform.

With the Citizen Developers group, citizen developers can access resources pertinent to their work without any unnecessary access clutter, leading to reduced overhead for your administrators.

To learn more about how the user group is integrated into the various services within the platform, refer to the product documentation.

Custom attribute mapping for AAD

While our existing AAD integration offers automatic attribute mapping, this release introduces the ability for organizations to use custom attribute mappings.

We're launching with custom mapping support for the Business unit attribute which allows you to map attributes like organization divisions with the Business Unit field in the UiPath platform. This mapping can enhance the contextual understanding of users in your organization and can help integrate user identities with services such as Automation Hub.

You can map the Business unit attribute based on Azure AD attributes or via SAML.

End of life for the Deployment Assistant

We are discontinuing support for the Deployment Assistant. This will allow us to focus on further developing and refining tools that bring you greater benefits.

We encourage all users to delve into our official documentation to understand the existing tools and features. Please share your feedback on our official documentation; your input is essential in helping us continually enhance and fine-tune our offerings to best serve your needs.


Improved troubleshooting experience

We have introduced a new CLI tool helping you troubleshoot and debug Automation Suite. The new tool is called uipathtools and contains a subset of uipathctl capabilities specific to health commands. To make sure you have access to mitigation steps in a timely manner, we plan to provide updates to uipathtools at a higher cadence than our standard releases.
The uipathtools and uipathctl CLI tools are here to provide all the diagnostics functionalities of the old Automation Suite Diagnostics tool,, which we have removed from our offering.

Improved SSO authentication

We have updated the process for enabling Single Sign-On (SSO) for ArgoCD, which now involves using a Dex configuration file and specified parameters.

Read more details in our documentation.

Bug fixes

  • Erratum January 2024: The replica cleanup script would incorrectly reclaim storage on the nodes. For more details, see the Storage reclamation patch troubleshooting article.

  • Previously, both scheduled and on-demand backups would fail after one hour of timeout. Now you can extend the timeout interval to three hours. For details, see Enabling the snapshot backup and On-demand snapshot backup.

  • On some occasions, the script did not properly update or read the ODBC connection strings. This behavior no longer occurs.
  • A failure would occur when trying to rerun the Automation Suite installer 90 days after the first execution. The installer generated self-signed certificates with a 90-day validity, and rerunning it prompted the revalidation of the already expired certificates.

Admin bug fixes

  • Automation Express licenses were available for allocation in on-premises deployments, despite them being solely intended for cloud environments. The issue is now fixed.

  • Data Service units were not granted to organizations that had Action Center - Named User licenses. The issue is now fixed.

  • When you deleted an organization, its licenses were not released. Now, any licenses allocated to an organization go back to the license pool once the organization is deleted.

  • The minLevel NLog setting in the config map was not being honored. The default minLevel is "Info" indicating that logs of "Info" severity and above should have been logged. However, the minLevel was not being considered, and logs with lower severity levels, specifically "Trace" and "Debug," were also being written to the logs.
  • Previously, there was an issue where well-known SIDs were inadvertently included when retrieving security groups, leading to unexpected behavior. Well-known SIDs are no longer included when fetching security groups, ensuring smoother and more predictable functionality.

  • After upgrading to version 2022.10.1 or later, logging into the host tenant, then logging out, and subsequently switching to a different tenant resulted in redirection back to the previous log-out location instead of the selected tenant. Now, after logging out and switching tenants, you will be correctly redirected to the selected tenant's page instead of the previous log-out location.

Known issues

Collation differences between SQL server and SQL database not supported

Erratum - added February 28, 2024: Stored procedures do not support collation differences between the SQL server and SQL database. To avoid any potential problems, you must ensure that the collation settings of both SQL server and SQL database are identical.

Upgrade fails due to MongoDB to SQL Server migration

Erratum - added February 28, 2024: We have identified an issue impacting the side-by-side upgrade of Automation Suite 2022.10 or earlier to 2023.10.0 and 2023.10.1. Due to a faulty migration from MongoDB to SQL Server, the upgrade operation fails if you have Apps enabled and use Kerberos authentication for the SQL Server database.

The recommended solution is to upgrade to Automation Suite 2023.10.2 or later instead.

Installation failure when adding new products to existing Automation Suite

Erratum - added February 28, 2024: Whenever trying to add a new product to an existing Automation Suite installation, the installer wrongly asks you to provide a temporary registry, causing a failure in the installation process.

To solve the problem, use the following workaround:

  1. Make sure the temporary registry is up.
  2. Change the readinessProbe setting of the docker registry StatefulSet by running the following command:
    kubectl patch statefulset docker-registry -n docker-registry --type json -p '[{"op": "replace", "path": "/spec/template/spec/containers/0/readinessProbe", "value": {"httpGet":{"scheme":"HTTPS", "path": "/", "port": 5000}}}]'kubectl patch statefulset docker-registry -n docker-registry --type json -p '[{"op": "replace", "path": "/spec/template/spec/containers/0/readinessProbe", "value": {"httpGet":{"scheme":"HTTPS", "path": "/", "port": 5000}}}]'

Issues affecting log forwarding to government cloud storage

Erratum - added December 19, 2023: You cannot forward Fluentd and Fluent Bit logs to Azure and AWS government cloud storage.

We recommend using Splunk and forwarding application logs there.

Zombie processes after performing an offline installation

Erratum - added December 19, 2023: After performing an offline installation, the Docker registry readiness probes trigger zombie processes.

To fix the issue, run the following command after performing a 2023.10.0 offline installation to update the existing readiness probes. This step is not required for online installations.

kubectl patch statefulset docker-registry -n docker-registry --type json -p  '[{"op": "replace", "path": "/spec/template/spec/containers/0/readinessProbe", "value": {"exec":{"command":["sh","-c", "[ -f /var/lib/registry/ready ] || { echo \"Registry is not seeded\"; exit 1; } "]}}}]'kubectl patch statefulset docker-registry -n docker-registry --type json -p  '[{"op": "replace", "path": "/spec/template/spec/containers/0/readinessProbe", "value": {"exec":{"command":["sh","-c", "[ -f /var/lib/registry/ready ] || { echo \"Registry is not seeded\"; exit 1; } "]}}}]'

After Disaster Recovery Dapr is not working properly for Process Mining and Task Mining

After a Disaster Recovery, Dapr is not restored properly, and the certificates needed by dapr to provide services for Process Mining and Task Mining are incorrect. The dapr, processmining, and taskmining applications appear to be healthy first, but will then go back to progressing state and the environment becomes unstable. When logging in to Process Mining or Task Mining, the application may not load, or return unexpected errors.

See Process Mining troubleshooting for a description of the steps you should take to resolve the issue.

Document Understanding Out of the Box Packages versions missing

In certain situations, the Out of the Box Packages installer can fail. If this happens, some ML Package versions will be missing in Document Understanding. To fix this, you can either trigger the ArgoCD sync, or wait until the ArgoCD sync triggers the installer automatically to reinstall the packages.

Character not allowed when setting connection string for Document Understanding

When setting the connection strings manually in the configuration file, Document Understanding database passwords cannot start with { for PYODBC.

AI Center provisioning failure after upgrading to 2023.10

When upgrading from 2023.4.3 to 2023.10, you run into issues with provisioning AI Center.

The system shows the following exception, and the tenant creation fails: "exception":" CKR_KEY_SIZE_RANGE
To resolve this issue, you need to perform a rollout restart of the ai-trainer deployment. To do this, run the following command:
kubectl -n uipath rollout restart deploy ai-trainer-deploymentkubectl -n uipath rollout restart deploy ai-trainer-deployment

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.

Internal component versions

This Automation Suite release bundles the following internal components:



































Was this page helpful?

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