Could updating the robot to version 24.2+ impact processes running on .NET 6.0-7.0?

I’m currently migrating processes that are in production. The current .NET version support is for .NET 6.0-7.0, and after migration, the package version will target .NET 7.0-8.0.

While testing the migrated process on the UAT system (which is running robot version 2024.10.0 preview), everything worked fine. According to this documentation, the package installed and ran successfully because the minimum required robot version for .NET 8.0 processes is 2024.2+, which my UAT robot meets.

However, when I attempted to install the same process on the PROD robot (assistant) running version 22.+ (I’ll provide the exact version shortly), I encountered the same error mentioned in the above documentation.

The solution, as per the docs, is to update the robot to 2024.2+. While this isn’t an issue, as I can download the UiPathInstaller MSI, my concern is whether updating the robot will affect any non-migrated processes that are still running in the PROD environment.

I’ve reviewed the following documents but couldn’t find a clear answer on backward compatibility:

These documents are interlinked and follow the sequence listed above.

Robots are backwards compatible as runtime and dotnet8 is backwards compatible. So upgrading only the robot without updating the processes should not cause any problems. In case you face any problems please raise a support ticket so we can look into it.

1 Like

But I have a doubt , why it is not mentioned anywhere in the docs z or if I have missed

Here is the documentation that mentions this.

Hey, thanks for sharing the docs. Yes, I have gone through this doc, as mentioned earlier, but I didn’t find it. Could you pinpoint it, please?

It’s the very last table. The link should jump to the Automation project section that mentions the project compatibility with robot version.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.