Unable to upgrade Test Automation process automatically on the folder
Issue Description
When a Test Automation package is published to Orchestrator, the associated process does not auto-update. Attempting to update it manually throws the error: "1 item(s) have not been updated (#156)."
Root Cause
The error occurs when the package version follows a four-segment numbering format (e.g., major.minor.patch.build), which is currently unsupported. UiPath only supports a three-segment numbering format for versioning (e.g., major.minor.patch).
Example Scenario
A Studio project is published for the first time with a package version using the three-segment format (e.g., major.minor.patch).
The package is successfully published and appears in Orchestrator.
The project is updated and published again using the same three-segment format (e.g., major.minor.patch).
The package is updated successfully in Orchestrator.
The project version is then modified to use a four-segment format (e.g., major.minor.patch.build) in Studio and published again.
In Orchestrator, the package appears in the "Packages" section.
When attempting to upgrade the associated process to the latest package version using the "Upgrade" option (ellipsis menu), the following error is displayed:1 item(s) have not been updated (#156).
Resolution
- Ensure that the package version adheres to the three-segment numbering format (e.g.,
major.minor.patch). - Avoid using a four-segment numbering format (e.g.,
major.minor.patch.build) when publishing projects from Studio.