Power Automation flow broke (?) with latest Edge update (Version 108.0.1462.46 (Official build) (64-bit)).

[Anonymous]

At about step 5 the flow should pick the middle of 3 tabs at a given web page.

Since updating Edge this morning I can see that it's selecting that tab - but it doesn't actually go to the page under the tab so that when a subsequent step tries to select a field under the middle tab, it don't find the field and fails.

Tried, so far unsuccessfully, various workarounds.  E.g. respecifying the UI element to select - however that's not really the problem.  The problem, as best I can see, is that events aren't firing after you select the tab to transfer focus there.

[CKN]

Check the plugin for Edge - you may need the new Manifest V3 version(especially if you have updated to PAD2.27).

[Anonymous]

Thanks.  Yes I'm at PAD 2.27.

As best I can tell I may have Manifest V3 already.  A new plugin today - in Browser | Extensions I have two PAD extensions - a first whose details tell me it's compatible with 2.27 and a second labelled Legacy.  Was wondering about that.

They were both enabled so I disabled Legacy but that didn't help.  My problem persists.

[CKN]

I can relate - I went through this yesterday with Chrome not finding the active window. At first the new plugin made no difference but a complete restart fixed that. Sorry to recommend a 'turn it off and on again' solution, but that's what it took to remedy it for me!

[Anonymous]

Tried that a first time and it didn't help.  Although that was before I turned off the Legacy plugin.  I'll give it another go.  Thanks for your feedback.

People ask me what to do about their computer problems.  My single most common response is: reboot, then if the problem persists let me know.

[CKN]

When the Windows H2 update came out, Automate wasn't picking up any active windows in browsers until there was an Automate update to 2.26 so it may be a case of the new Edge needs a patch for Automate. Can you use Chrome instead as a temporary work around? You will need to redo the flow and make sure you have the 2.27 Chrome plugins but it would address any issues with the new version of Edge

[Anonymous]

I seem to be on a detour.  Rebooted and when I ran PAD it wanted to install 2.26!  Wtf.  Checked About - I'm somehow back at 2.25.

Ran flow; it complained about the plugin; turned off the new one and turned Legacy back on.  And, unsurprisingly, it works again.

I try and stay away from Chrome.  I started with it but then had problems that sent me to Edge.

I have something that works again which is good however past experience is that you can only tell PAD Updates No for so long before they won't let your flows run.

Hmm.  I suppose I should get back to doing my actual work.

[Anonymous]

Knew this would happen.  2.25 mysteriously upgraded itself back to 2.27 and my flow is again broken. 

I use "Click link on a web page" to select 1 of 3 tabs on the top row of a particular page at a private site.  It selects the tab but then doesn't change focus to the page under the tab with the result that the next steps are meaningless - and break.

I could 1) try to reinstall a previous version - although it's not clear to me how to do that 2) find some kind of workaround 3) search the web for locations where Microsoft lists outstanding problems so that I'd at least know that they're aware of what I'm looking at (provided I'm looking at it correctly).

[CKN]

It seems a lot of people are finding a re-install useful, not from the store but the MSI installer. Also meant taking all drivers from their browsers and letting this process install them. This has the link to the installers and more people who have been having issues that have been fixed. It also explains why it isn't happening to everyone

https://powerusers.microsoft.com/t5/Power-Automate-Desktop/power-automate-desktop-not-connecting-to-...

[Chadillac]

Worked for me, but only if I restarted after the uninstall, then re-installed AFTER the restart. 

[Anonymous]

Hmm thanks for the suggestions but, no, that didn't work for me.

Downloaded the MSI; uninstalled PAD; rebooted; installed from the MSI.  My flow still fails in the same way.  I want to select a tab in a row of three tabs and go to the page below that tab.  That is, selecting the tab needs to open and draw the new page.  With 2.27 (had worked fine with previous versions which I'd been running for months since first writing the flow) the target tab is highlighted (my #1) but the browser doesn't open the new page under that tab (#2).  Steps after that expect to find UI objects on the new page; they're not there; and the flow fails.

Back to the drawing board.  People talk about getting previous, old, versions of PAD from Microsoft - how does one go about doing that?  Either 2.25 or 2.26 would do the trick.  I was, at a point, serendipitously back at 2.25 (don't ask me how that happened because I don't know) and my flow worked just fine again.

[ryule]

I would like to know this too (where can we download prior versions). My bots are failing more than they are succeeding with 2.27, and it's unacceptable.

[Anonymous]

Hmm, just did a test.  Used Chrome and recreated enough of my flow to get to the error.  Chrome doesn't have the problem so it would appear to be Edge-specific.  Edge and Windows both are fully updated.

On the other hand, Chrome, at least a couple of months ago, had other problems and I'm disinclined to recreate all of a somewhat long flow only to find that it still has the Chrome problem.

[Anonymous]

Found an old 2.25 install kit in my Downloads directory and my flow is working again.  Obviously, the solution I'd prefer is if the latest version worked properly.  Again - my experience is that Edge has the problem but Chrome does not.

[ryule]

Yeah, I reverted to 2.26 and reverted my extension back, and all is well. Something is definitely up with 2.27.

[ryule]

I had a call with a Support Engineer from Microsoft's Power Platform team this morning on my 2.27 issues. I had since reverted both of my machines to 2.26, and have only been running one in my Machine Group due to other issues on our end (which are now resolved).  Anyway, had me uninstall the Legacy Power Automate extensions prior to upgrading PAD, and then we upgraded PAD, and then installed the new browser extensions from within one of my bots in the designer (Tools > Browser Extensions), and of course it worked both attended and unattended. If you would've asked me, I'm sure I've taken those exact steps before, but perhaps not. So I'm going to throw that machine back into my Machine Group and will actively monitor it. (fingers crossed it wasn't a fluke)

[Anonymous]

OK that's interesting - I'll keep it in mind.  For the time being though, I'll stay at 2.25 - it suffices for my needs.  Then when > 2.27 comes out, I'll try that.  Not entirely logical I suppose, but that's fine.