Subscribe

Overview

Product lifecycle support terms

The Product Lifecycle describes the support periods for UiPath on-premise products. You can use this information to track how long a particular version of a product is supported, to schedule your software installation or upgrades, and benefit from continuous support.

This Policy is a part of, and must be read together with, the Support and SLA Policy available here. For an easier read, we avoid using too many capitalized terms in our technical documentation, so if this Policy refers to software, products, customer, or documentation, the definitions in the Support and SLA Policy or in your licensing agreement with UiPath apply. If you do see capitalized items, refer back to the said Support and SLA Policy or licensing agreement. Also, you are the customer, as defined by our legal documents.

Some things we want you to know or do:

  • In order to receive support for a product, you must have installed and use the latest released version of the supported Major version of a product.
  • Updates on the supported Major version are cumulative, with each update built upon all of the updates that preceded it.
  • UiPath does not guarantee forward compatibility between products, except as otherwise mentioned in our documentation.
  • UiPath guarantees backwards compatibility between two consecutive released versions of the UiPath on-premises products. Breaking changes, if any, will be reflected in a compatibility matrix published in our documentation. If backwards compatibility between two consecutive LTS versions cannot be guaranteed, UiPath may assist you in the migration process.
  • UiPath does not guarantee that all updates will work on all devices. Update availability or applicability may vary depending on conditions, for example by country, region, network connectivity, or hardware capabilities.
  • Support for localized versions, minor updates and connected software (e.g. SDKs, connectors) of a major version terminates with support for the major version.
  • Fixes that imply database changes will be done exclusively on the latest released version.

UiPath support periods

For detailed information on supported version for each product, see Product lifecycle.

General Availability support

UiPath issues Fast Track Support (FTS) and Long Term Support (LTS) versions of the UiPath on-premises products.

Support type

Mainstream support

Extended support

FTS

6 months from the release date

6 months from the end of Mainstream support

LTS

24 months from the release date

12 months from the end of Mainstream support

Each FTS and LTS version will benefit from Mainstream and Extended support based on the table above.

Mainstream support

Products are fully supported, meaning that UiPath will provide customers with Incident support, bug fixes/workarounds, security updates and responses to Service Requests. At the end of the Mainstream support period, customers will need to update to a version available in Mainstream support to remain fully supported.

Extended support

Products will only receive partial support, meaning that UiPath will provide customers Incident support and critical security fixes on a commercially reasonable basis. Technical support troubleshooting may include recommendations to update to a version available in Mainstream support. At the end of Extended support period, Customer is required to update to a version available in Mainstream support or Extended support to receive support.

Out of support

UiPath will no longer provide any type of support. You must upgrade to a version available in Mainstream or Extended support to receive support.

UiPath Activities support periods

For detailed information on supported version for each Activity, see Activities lifecycle .
All activity packages follow the semantic versioning format = Major.Minor.Patch.

Availability

All versions published on the official UiPath NuGet feed will remain available unless exceptional circumstances require removal (e.g. security concern).

Supported type

Versions released as part of an on-premises product release (e.g. bundled in the 2020.4 FTS Studio or Orchestrator installer) will follow the same support cycle. When there is no new version of an activity in a GA release, the last released version will inherit the support period from the latest GA release.
Newer versions released and published on the official feed between on-premises releases are supported and will inherit the support model of the upcoming release with the exception of patches, which will continue to follow their corresponding version support.

Note: Any published bug fix will ship as a new patch release (increment of the Patch version) atop the latest Minor version codebase. E.g. let's say that 3 minor versions of the Excel activity package are currently supported (time of this writing): 2.5 (2019.4 FTS), 2.7 (2019.10 LTS), and 2.8 (2020.4 FTS). Current patch versions are 2.5.4, 2.7.2, and 2.8.5. If a defect is found in 2.5 and deemed critical enough to require a bug fix release, then a 2.5.5 package will be created by applying the fix to the 2.5.4 codebase. Even if the defect affects 2.5.1, there will be no in-between release such as 2.5.1b, and customers will need to upgrade to 2.5.5 to benefit from the fix.

About out-of-support Activities versions

Due to the dependency management mechanism of UiPath Studio and Robot, starting with version v2018.3, workflows may continue to rely on specific package versions beyond their support period. It is common practice to keep using package versions that are out of support for existing production automations that operate nominally and have no need to be modified. As bug fixes and improvements may affect the behavior of existing automations, upgrading to newer versions is only recommended when serving an explicit purpose, such as applying a bug fix, supporting target application upgrades, or other technical motivation.

Updated about a month ago

Product lifecycle support terms


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.