- Backward Compatibility - Refers to our platforms' ability to interact with older versions of the UiPath suite.
- Forward Compatibility - Refers to our platforms' ability to interact with future versions of the UiPath suite.
Studio and Robot always need to have the same version. For the compatibility matrix between Orchestrator, Robot, and Studio, please see this table.
Projects created with alpha or beta Studio versions might not be compatible with newer Studio builds, nor can they be executed by newer Robots.
The versions of activity packages are not at all dependent on the versions of Studio, Robot, or Orchestrator. The only exceptions are Orchestrator-related activities. For example, the Start Job activity, which was introduced in the 2018.1 version, only works with Robots of that version or higher.
We support backward compatibility, with the exception of breaking changes announced in official release notes.
Projects created with older versions of Studio (prior to v2018.4) can be executed on newer Robots (v2018.4 and higher) after its dependencies are migrated, as explained here.
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 v2018.3 might not work with a v2017.1 Robot.
The following table lists what version of Robot and Studio works with what version of Orchestrator. Patches are implicitly supported in this matrix unless specifically mentioned here.
Please note that by not upgrading to the latest available version you are not taking advantage of the newest features or bug fixes added in our releases. You only have access to 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.
Updated about a year ago