Need Guidance on Handling Version Compatibility Issues (2023.10.3)

Help Activities
, ,
1

Hi everyone,

We currently have UiPath version 2023.10.3 installed across all our development VMs. While this version has been stable for our existing processes, I’m facing challenges utilizing new features and updates introduced in later versions.

Whenever we try to upgrade to a newer version, some of our older processes start breaking due to compatibility issues. This is making it difficult to take advantage of the latest improvements in UiPath without risking the stability of our current automations.

Has anyone faced a similar situation?
I’d really appreciate any suggestions or best practices on how to:

  • Safely upgrade to newer versions without impacting existing workflows
  • Manage version compatibility across multiple projects
2

Hi @nvignesh456
Use a test VM to validate upgrades, follow the UiPath Compatibility Matrix, modularize libraries, upgrade incrementally (e.g., 2023.10 → 2024.4), and align Studio/Robot versions on each machine.

For more: Overview - Compatibility matrix

If helpful, mark as solution.
Happy automation with UiPath

3

I am slightly confused with the answer. I gone through the compatibility matrix. Still not getting anything properly..

Let me know the steps. Thanks buddy :slight_smile:

4

@nvignesh456,

If you are also upgrading the project from Legacy to Windows while updating the Studio version, these errors are quiet possible to happen because it’s going to change the underneath version of the .Net runtime.

There isn’t a sure shot error free way to upgrade but you can follow the best practices while doing this upgrade.

5

@nvignesh456

First try to upgrade the packages in your process and then try to open them in new studio version that should align most of the activities

Also while doing this try to upgrade one system and then test the processes or open processes there and then slowly upgrade the remaining systems

Cheers

6

1.Try to open UiPath studio with source code and update the required package activity.
2.publush that updated UiPath to orchestrator.
3.once you update you will get update option in orchestrator process just update that.

Hope will help
Please mark solution if its help :blush:

7

Hi @ashokkarale , @Anil_G

This thread is matching with my query related to project upgrade to latest UiPath Studio LTS version, what I have observed is that the project.json file does not update the studio version even through the project opened in new UiPath studio and I can successfully publish the project for testing.

Is it a known behavior of UiPath studio and should I update the studio version in project.json file manually?