Unanswered

Browser Automation Error

(0) Share

Report

Posted on by CooneyRTX

Recently an update was applied in PAD and since when I use Launch New Microsoft Edge, I get an error: Failed to assume control of Microsoft Edge (Internal error or communication failure). I am using the most recent version of PAD. Any ideas as to how to resolve the issue?

Thank You

Categories:

Power Automate Desktop

I have the same question (0)

All responses (14)

Answers (0)

NathanAlvares24 1,714 Moderator on at

Like (0)

Report

Hi @CooneyRTX !

That error message suggests that there is an issue with the communication between the browser automation tool you're using and the Microsoft Edge browser.

So instead, try using the 'On error' -> 'Continue flow run' -> Exception handling mode as 'Repeat action' to keep running the action until success.

If the error still persists, check the Browser Settings as they may need to be adjusted to allow automation. For instance, check for browser extensions or settings that might be causing conflicts.

Or a simple restart will do.
----------------------------------------------------------------------------------------------------------------------------------------
If this helps & solves your problem, please remember to give a "Thumbs up" and accept my solution as it will help others in the future.

Was this reply helpful? Yes No
NathanAlvares24 1,714 Moderator on at

Like (1)

Report
Another method is this:

Try launching Edge via the Run application action and then using Launch new Microsoft Edge to attach to it. The flow should look somewhat like this:

Note: I initially run Edge with the Google page to make it load faster and also make it easier to attach to the instance. This is a standard functionality I always use in every single flow.
Also note: You will need to replace the value of the %URL% variable in the Set variable action to whatever you want to navigate to.

Here's a snippet that you can copy and paste directly into your PAD flow designer to create all those actions:
SET URL TO $'''www.someURL.com''' System.RunApplication.RunApplication ApplicationPath: $'''msedge''' CommandLineArguments: $'''www.google.com''' WorkingDirectory: $'''%''%''' WindowStyle: System.ProcessWindowStyle.Maximized ProcessId=> AppProcessId WAIT (UIAutomation.WaitForWindow.ToOpenByTitleClass Title: $'''Google*Microsoft Edge''' Class: $'''Chrome_WidgetWin_1''' FocusWindow: True) FOR 30 WebAutomation.LaunchEdge.AttachToEdgeByTitle TabTitle: $'''Google''' AttachTimeout: 5 BrowserInstance=> BrowserMain ON ERROR REPEAT 5 TIMES WAIT 3 END WebAutomation.GoToWebPage.GoToWebPageCloseDialog BrowserInstance: BrowserMain Url: URL

Source of the above information: https://powerusers.microsoft.com/t5/Power-Automate-Desktop/Microsoft-Edge-Browser-Error-when-launching-pages-in-new/m-p/2419291#M32895

Regards,
Nathan Alvares

Was this reply helpful? Yes No
dashort 62 on at

Like (0)

Report

I have encountered the same issue with the same timing. It has affected all three browsers and the error message is the same. I have used the PAD flows for years...

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like (1)

Report

I suggest trying to use the Run application method and then attaching to the browser afterwards. @NathanAlvares24 has posted a copy of that method above.

If that doesn't help, you may need to report this as a bug to MS support.

-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.

Was this reply helpful? Yes No
CooneyRTX 23 on at

Like (0)

Report

NathanAlvares24,
Thanks for the suggestion. I tried this and the flow just sat in what appeared to be an infinite loop.

Was this reply helpful? Yes No
CooneyRTX 23 on at

Like (0)

Report

dashort, I am in the same boat. I hope they do an update soon or I will have to look for other solutions. It was working fine prior to the last update. Good luck!

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like (0)

Report

Have you tried the other approach with Run application?

Was this reply helpful? Yes No
CooneyRTX 23 on at

Like (0)

Report

The action wait for window times out on me.

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like (0)

Report

Can you share a screenshot of your flow?

Was this reply helpful? Yes No
CooneyRTX 23 on at

Like (0)

Report

Agnius.....the issue is still present. It occurs if I open any web page. The screenshot below shows just opening google generates an error. I did see another user on another board indicate that they reported this to MS and they are working on the issue with no ETR.

Was this reply helpful? Yes No