GoToWebPage fails: Page didn't load or lost communication across flows since March 19, 2026

(3) Share

Report

Posted on by CU-18081637-0

Hi all,

I want to check whether others are seeing the same issue recently.

**Environment**
- Power Automate cloud flow calling a Power Automate Desktop flow
- Error started recurring on March 19, 2026
- Affects multiple PAD flows, not just one
- Web automation scenario

**Observed error**
Action 'Run_a_UI_flow_for_web' failed

Problem while executing action 'GoToWebPage'. Failed to navigate.
Failed to wait for page to load.
Page didn't load or lost communication with browser.

**Context**
- These flows were working before
- The problem started recently and seems to affect different PAD flows
- I suspect a recent PAD/browser/extension update, but I have not confirmed root cause yet

**Questions**
1. Is anyone else seeing the same "GoToWebPage" / "lost communication with browser" error recently?
2. If yes, which PAD version and browser version are you on?
3. Did anything help, such as reinstalling the browser extension, switching install type, or changing browser automation mode?

**Notes**
- This appears during a cloud flow run that invokes PAD
- The failure message suggests browser communication or page-load handling issues

Thanks — I’m posting this mainly to see whether this is a broader regression.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (15)

Answers (0)

Sort by

SM-19031039-0 6 on at

Like (2)

Report
Copy link

Link copied!

I am seeing the same issue across a lot of my web based flows since yesterday/day before. Nothing has fixed it other than disabling the 'Wait for Web Page to Load' advanced feature, which isn't ideal

Was this reply helpful? Yes No
Ryan_Aldridge 25 on at

Like (1)

Report
Copy link

Link copied!

Hi,

We have been having the same issue for the last few days and had assumed it was a local network problem that was causing extended page loads to hit the default 60 second timeout but we've just noticed this morning that the Go To action is failing after less than 1 second. The only thing we've really tried is a server reboot. We are running version 2.65 so I think my next step is going to be to try and reproduce the problem in a test environment and then maybe try 2.66 or rolling back to 2.64.

Was this reply helpful? Yes No
AF-17031117-0 8 on at

Like (2)

Report
Copy link

Link copied!

Hey

We're having the same issue our end, flows that have been working for over a year have just starded randomly failing at different go to webpage and click link actions.

hoping someone has a resolution for this.

Was this reply helpful? Yes No
VM-20031118-0 10 on at

Like (2)

Report
Copy link

Link copied!

Facing the same issue for multiple flows which were running fine for years. Did we identify a fix for it?

Was this reply helpful? Yes No
Ryan_Aldridge 25 on at

Like (1)

Report
Copy link

Link copied!

we tried a roll back to PAD 2.64 and an upgrade to 2.66. Neither helped. We noticed there was a new version of EDGE released this week and it has been automatically updated on all of our devices. We're not currently able to roll that back .

Was this reply helpful? Yes No
Highboy 1,185 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

We are facing the excat same problem, failing on goto webpage and clicks on ui's - scripts have been working perfect for years.
Please Microsoft - do something

Was this reply helpful? Yes No
CU23030714-0 3 on at

Like (0)

Report
Copy link

Link copied!

Did anyone get any solution? Or any response from Microsoft Team?

Was this reply helpful? Yes No
Suggested answer

RR-24031331-0 2 on at

Like (0)

Report
Copy link

Link copied!

Afternoon,

Glad I stumbled onto this forum.

- I had the same issue.

- I tried reinstalling the extensions

- Tried creating a new flow

- Changed the action delay time to 1000ms

- Added a wait action between each block

None of the above helped.

What did eventually work for me was changing the browser my flows use from Edge to Chrome. This has fixed the issue for me.

Not entirely sure why Edge (MS Product) is no longer working with Power Automate but Chrome is working and that's enough for me.

Hopefully this workaround helps others until MS fix the problem.

Was this reply helpful? Yes No
NC-20030407-0 6 on at

Like (0)

Report
Copy link

Link copied!

Same issue here. It looks like the browser and Power Automate lose connection to each other and so flow fails. Still waiting on MS to provide a solution.

Was this reply helpful? Yes No
Ryan_Aldridge 25 on at

Like (0)

Report
Copy link

Link copied!

Rolling back to EDGE version 145.0.3800 resolved the issue for us but it is only a temporary solution as our information security team wont allow us to use an outdated browser for more than a couple of weeks.

Was this reply helpful? Yes No