The below matrix provides information about the interoperability between Orchestrator and Robot and Studio, Test Manager, AI CenterTM, Insights, and Action Center according to their versions and Orchestrator's delivery model. Patches are implicitly supported in this matrix unless specifically mentioned otherwise.
By not upgrading, you are restricted to using the features of the smallest installed version of either Robot or Orchestrator.
It is usually recommended to first upgrade your Orchestrator and then your Robots. In this scenario, the Robots have to be reconnected to Orchestrator after the update.
Some versions are no longer supported. Please refer to the product lifecycle for more information. An out of support version of a product is only compatible with another product having a supported version until the next patch release. For example, Orchestrator 2021.4, which is currently out of support, is only compatible with AI Center 2021.10 until the next patch release after the out of support date of Orchestrator.
Note: Out of support versions are removed from the Compatibility matrix table six months after their support ends.
- Compatible - Not compatible
|Product Version||Orchestrator 2022.10.x||Orchestrator 2022.4.x||Orchestrator 2021.10.x||Orchestrator 2021.4.x||Orchestrator 2020.10.x||Orchestrator 2019.10.x|
|Build||Studio 1||Studio 2022.10.x||8, 9||8, 9||8, 9||8, 9|
|Studio 2022.4.x||8, 9||8, 9||8, 9||8, 9|
|Studio 2021.10.x||8, 9||8, 9||8, 9||8, 9||8, 9|
|Studio 2019.10.x||2, 3, 4||2, 3, 4||2, 3, 4||2, 3, 4||2, 3, 4|
|Run||Robot 1||Robot 2022.10.x||8, 9||8, 9||8, 9||8, 9|
|Robot 2022.4.x||8, 9||8, 9||8, 9||8, 9|
|Robot 2021.10.x||8, 9||8, 9||8, 9||8, 9||8, 9|
|Robot 2019.10.x||2, 3, 4||2, 3, 4||2, 3, 4||2, 3, 4||2, 3, 4|
|Manage||Test Manager||Test Manager 2022.10.x|
|Test Manager 2022.4.x|
|Test Manager 2021.10.x|
|Test Manager 2020.10.2+|
|AI Center710||AI Center 2022.10.x|
|AI Center 2022.4.x|
|AI Center 2021.10.x|
|AI Center 2020.10.x|
|Engage||Action Center||Action Center 2022.10.x||N/A|
|Action Center 2022.4.x||N/A|
|Action Center 2021.10.x||N/A|
|Action Center 2021.4.x||N/A|
|Action Center 2020.10.x||N/A|
1 - Studio and Robot always need to have the same version when installed on the same machine. For example, if you have Studio 2022.4.x installed, Robot must be v2022.4.x as well. This also applies to Studio Pro. For more information on the compatibility between Robot and projects created in different versions of Studio, see the Automation Projects section.
2 - Robots 2018.4.4+ and 2020.4- connect to Orchestrator via Long Polling only.
3 - TLS 1.1 / TLS 1.2 must be enabled.
4 - Robots 2019.10 and older cannot execute unattended processes in modern folders.
5 - Robots 2019.4 and older only work with classic folders.
6 - Robot SignalR authentication is not configurable and is enabled by default to ensure secure communication between Orchestrator and Robots. As such, you can only use 2018.4.4 Robots or above.
7 - This compatibility applies to UiPath Document Understanding as well since it is built on top of the AI Center infrastructure.
8 - You need Robots and Orchestrator 2021.10+ to execute Windows and cross-platform processes.
9 - You need Robots 2021.10+ to execute background processes without credentials.
10 - This compatibility applies in the case of AI Center connected to an external Orchestrator.
UiPath Process Mining and Task Capture work as standalone products and do not require a compatibility matrix. Even so, for the best experience, the following requirements must be met:
- For Process Mining and Automation Hub integration, you need to have at least 2021.4 for both products in Automation CloudTM.
- To run Task Capture from Automation Hub in Automation CloudTM, Task Capture needs to be at least 2020.10.4 or above.
- To run Task Capture from Test Manager, Task Capture needs to be at least 2020.4 or above.
- To run Task Capture from Task Mining, Task Capture needs to be at least 2021.10 or above.
- To run Task Capture from UiPath Assistant, both Task Capture and UiPath Assistant need to be at least 2021.10 or above.
Products in Automation Suite are delivered as part of a single bundle and always have their versions in sync. See Automation Suite components in the Automation Suite guide for details on the products that are part of the suite.
The following Robot/Studio versions are supported against Automation Suite.
- Compatible - Not compatible
|Robot and Studio 2022.10.x||Robot and Studio 2022.4.x||Robot and Studio 2021.10.x||Robot and Studio 2021.4.x||Robot and Studio 2020.10.x||Robot and Studio 2019.10.x|
|Automation Suite 2022.10||1, 2||1, 2||1, 2|
|Automation Suite 2022.4||1, 2||1, 2||1, 2|
|Automation Suite 2021.10||1, 2||1, 2||1, 2||3, 4|
1 - You need Robots 2021.10+ to execute .NET 5+ processes.
2 - You need Robots 2021.10+ to execute background processes without credentials.
3 - Robots 2018.4.4+ and 2020.4- connect to Orchestrator via Long Polling only.
4 - TLS 1.1 / TLS 1.2 must be enabled.
5 - Robots 2019.10 and older cannot execute unattended processes in modern folders.
6 - Robots 2019.4 and older only work with classic folders.
UiPath guarantees backwards compatibility between two consecutive released versions of the UiPath on-premises products (standalone and Automation Suite). Breaking changes, if any, will be reflected in this compatibility matrix. If backwards compatibility between two consecutive LTS versions cannot be guaranteed, UiPath may assist you in the migration process.
For Orchestrator services residing in Automation CloudTM, we ensure backward compatibility with the three latest enterprise Robot and Studio releases.
|Cloud Orchestrator Service|
|Latest Robot and Studio version|
|Second-latest Robot and Studio version|
|Third-latest Robot and Studio version|
If you are currently using the third-latest Robot version, you should make arrangements to upgrade the Robot before we release the next Robot version to avoid compatibility issues.
Some versions are no longer supported. Please refer to the product lifecycle for more information. We don't support interoperability between two products if one of them is out of support.
Activity package versions are independent of Studio, Robot, or Orchestrator versions, except for Orchestrator activities. For example, the Start Job activity, introduced in 2018.1, only works on 2018.1 Robots or newer.
Projects created with alpha or beta Studio versions might not be compatible with newer Studio builds, nor can they be executed by newer Robots.
We support backward compatibility, except for breaking changes announced in the official release notes, and following the product lifecycle.
Newer Robots can execute projects created with older versions of Studio. For example, a project created with Studio 2018.4 should work on a 2019.10 Robot or newer.
We do not support forward compatibility. Projects created with newer versions of Studio might not work with older Robots. For example, a project created in Studio 2019.10 might not work with a 2018.4 Robot.
Updated about a month ago