could it be the case that the versions are swapped, otherwise it looks like a downgrade
Let us clear sort out
- UiPath Studio Version
- Workflows made with a particular Studio Version
Workflows are done with a UiPath Studio and are built with the consumption of referenced nuget packages. Here the project.json defines the dependencies to the packages and its versions
A particular Studio Version comes with new features- compared to other versions - ,functionalities , Bugfixes and maybe also Bugs within the IDE.
In short: Using a newer UiPath version is not mandatory upgrading the the referenced packages also to a newer version (when not wrongly touched the dependency definitions)
In other words: Even with a Studio 2020.X we can define dependencies for a workflow which are on a newer level e.g. 2021.X
– a UiPath Studio
- most often: the above described independend things are mixed up and unwanted package upgrades are done
- new created projects are started on an unwanted package level (does mean, we want to work with the newest UiPath Studio Version, but till End of particular period also new modelled projects are to be defined on a didicated package version level. Unwanted the project was started with a different version)
And now also coming more to your question from another viewpoint. Incompabilities when UiPath version swithing can be found on release notes and package constrraints