Issues in Upgrade Power Automate Desktop to higher version in production setup

Like (1) Share

Report

Posted on 21 Apr 2025 13:36:59 by IshaS161

Hi All,

I'm assisting in an upgrade to Power Automate Desktop version from v2.45 to 2.52. The 2.45 version currently runs ~100 bots . Have there been any issues seen post migration generally (even if not its this version specific)?

I'm aware there was a time when:

Version 2.27 had caused issues with Browser Automation in the past, so people had to apply hotfixes or upgrade to 2.31.
Version inconsistencies on different machines can cause problems (even today).

I'm also aware that there's backward compatibility so things should not break ideally. I'm specifically concerned if any business application automation (SAP, Oracle etc.) can get impacted by this upgrade.

Apologies for putting the question in an incorrect category, I'm only getting Process Advisor and Licensing options here.

Categories:

Process Advisor

All responses (2)

Answers (0)

IshaS161 28 on 23 Apr 2025 at 10:39:51

Like (0)

Report

Issues in Upgrade Power Automate Desktop to higher version in production setup

Thanks Michael :)

Yes its that nervousness which makes everyone underconfident about upgrading, especially with so many bots. I don't think the team will roll it out in one go; that'd be unwise. They will most likely follow the verification one by one. They're just trying to be more aware of any potential issues beforehand, keeping people's experiences in mind, and save some time in testing.

Treating it like your own code is great advice. I'd definitely test enough to make sure my bots perform as expected!
Michael E. Gernaey 45,110 Super User 2025 Season 2 on 22 Apr 2025 at 02:10:22

Like (0)

Report

Issues in Upgrade Power Automate Desktop to higher version in production setup

hi

Your question is just fine where it is :-) but appreciate the note.

I hate to say it, but no one here is going to be able to scratch that nervous itch and be sure you won't run into issues. Its a shame, to say that, but it appears after every release there are things that are breaking and to what extent... its unknown until it happens.

do you have to upgrade everyone at once? Or can you do a verification set of rollouts? That would be my recommendation (as usual). I treat these types of updates as if I wrote the code.

User acceptance and backwards unit testing have to pass before I populate it all the way up the chain.

Thats my 2cents and i'd like 1.99 back please :-)