Multiple Flow Issues in Browser

[jusTodd]

A desktop flow working just fine for over a year now has suddenly turned in its resignation, and Power Automate has decided it no longer cares either.

In EDGE, 

• Populate text field on web page fails to populate.
  
  • It acts as if it does, but really does nothing.
• Click link on web page fails to click

Have tried simply adding a new step, but Power Automate UI selector can't even find the text field or the link to click.  The red box identifies everything except those points.  It is as if it lost its mind and does not know where anything is any longer.

Any thoughts are helpful.

[jusTodd · Accepted solution]

Just confirmed this is a Microsoft EDGE issue.  Should have thought to check before posting.

The same flow that worked perfectly in Edge for the last year, suddenly does not.

This same flow works perfectly in Chrome with no adjustment, except to Launch Chrome instead.

Checking on a couple of other flows that have been working perfectly in Edge also have the same issue.

That is not helpful, Microsoft.

[eetuRobo]

Sounds like maybe the website has had an update and maybe the text field and link has different UI elements. It of course should then fail but maybe there is still some hidden old elements or something that PAD finds but they do nothing actually in the web page. 
If you use Test button in the UI element for the text field does it find the element? 

And you said you cant re capture the elements since UI selector doesn't seem to recognize them. If you use Inspect on the element can you check if the element seems to be correct when you compare it to your capured element? Maybe take screenshot of both Inspect and UI-element so that we can better see what might be the issue. Like so:

PAD UI element:

Inspect view in browser:

[jusTodd]

Thanks @eetuRobo ... as noted above, this is exclusive to Edge.

[jusTodd]

No longer only Edge. This problem found its way over to Chrome.

Change my entire flow to use Chrome on Friday and it worked perfectly every time.

Today.  No.

[jusTodd]

Update. Google Chrome appears to have fixed their issue.

Still waiting on Microsoft Edge to fix their side.

[jusTodd · Accepted solution]

More extensive testing revealed that this is very likely a defect in Power Automate and not Edge.

When I replaced Edge with Chrome originally, I did not adjust the Window State under Launch Browser.

That is where the problem lies and what I logged feedback for.

Flows no longer function correctly when "Windows State: Maximized."

Changing to "Window state: Normal" appears to fix the problem.

This is true regardless of Chrome or Edge.

[Deenuji]

@jusTodd 

Completely strange scenario!! Thank you for sharing your insights with us.