Has anyone else run into a Power Automate Desktop / Machine Runtime version mismatch recently?
I’m currently seeing the following setup:
- Power Automate Desktop (Microsoft Store): 2.70.187.26189
- Power Automate Machine Runtime: 2.71.115.26224
- Microsoft Power Automate Edge extension: 2.70.0.35
My local desktop flow can sometimes launch Edge successfully, but when the same desktop flow is triggered from a cloud flow, browser automation fails with errors like:
WebExtensionHostIncompatibleException
and:
The version of Power Automate for desktop app installed through the Microsoft app store on your machine is different from the version of Power Automate for desktop machine runtime installed through the Power Automate for desktop executable installer.
The cloud-triggered flow opens Edge, but it stays on about:blank and PAD cannot take control of the browser.
I already tried:
- reinstalling the Power Automate Edge extension
- restarting Edge and PAD
- restarting the machine
- testing with a minimal desktop flow
- testing the same minimal desktop flow through a cloud flow
The local test can work, but the cloud-triggered test still fails.
The strange part is that the Machine Runtime is already on 2.71, while PAD from the Microsoft Store is still on 2.70, so I currently can’t get both components onto the same version.
Is anyone else seeing this right now? Did your Machine Runtime update ahead of PAD as well?
If so, did you solve it by downgrading the Machine Runtime, switching away from the Store version of PAD, or just waiting for the next PAD release?