Machines getting disconnected after attaching to Edge

[mariabarros]

Hey guys!

I'm currently testing a process in runtime (BP version 6.10.2) that opens a website in Microsoft Edge, accesses our ERP system, returns to our website, and navigates to another page.

The issue arises when the process tries to attach to the website after the ERP system. At this point, the machine disconnects unexpectedly. (Example below, I was checking the process running on machine CANWBPAAV04D)

I already tried mapping elements using Web mode (stopped working after a few tries even in debug), UI mode, Region mode, and even through TABs count, which is risky (I know). Everything seems to be fine, because other processes run OK, but it seems that Edge is an issue, even though I switched FROM Chrome because I was having trouble mapping. The disconnection consistently occurs during navigation steps, and there are no apparent issues with the machine or its connection. 

We’re currently blocked and would appreciate any assistance or guidance to resolve this. Thank you!

[grbanares]

This usually happens when either there is a code issue or machine memory concern. Maybe check the RAM if you are on prem or the equivalent for cloud. Try to increase the machine memory and see how it goes.

[SayeedBinAbdullah]

Hi @mariabarros 

As @grbanares mentioned correctly this might happen due to machine memory issue, you can also check if it is happening due to any of the below reasons,

Reason 1: Verify if the Edge version, WebDriver version, and Blue Prism browser extension version all match.

For example: If Edge version is v127.0.6533.72, your EdgeDriver must be exactly of that version.

Also, ensure the Blue Prism Browser Automation Agent service is running and not being killed by group policy or antivirus or is not blocked by firewall.

Note:- You can test stability by running a short process that only launches Edge, attaches, and navigates multiple times. If the machine disconnects even in this loop, the WebDriver handshake is likely failing.

Reason 2: Blue Prism’s Attach and Detach operations with modern browsers are session-sensitive.

For Example if you are trying to perform below operation

Step 1 - Launches a website (Edge instance 1)

Step 2 - Switches to ERP (possibly a different session)

Step 3 - Returns to the website (Edge instance 2 or a refreshed tab)

it might actually be dealing with a new browser process ID, breaking the link.

Try to use “Browser Mode – Attach by Title” instead of Process ID.

After navigating to the ERP system and returning, explicitly “Detach” and “Re-Attach” to the new browser window.

Add a wait stage before reattaching (1–2 seconds) to allow Blue Prism to detect the new DOM properly.

Note:- You can identify browser processes with tasklist /v | find "msedge" to verify whether Edge is creating new instances during navigation.

Best Regards,
Sayeed Bin Abdullah

[stepher]

Good morning,

Two questions and a thought... 

Q1. Are you seeing your process go into a 'Warning' state in the Control Room?  Or does it just outright fail?  I have often seen when the 'Warning' state is shown, the Runtime first locked up and then basically disconnected.  As mentioned above, this could be due to memory issues or coding issues.

Q2. What version of Edge are you currently using?  Ideally, you are not on version '140.x'.  There is a whole thread on the issues introduced by version 140 of the Chromium engine.  In certain cases, it enters an infinite loop looking for UIA elements.  This infinite loop would lead to the 'Warning' state I was mentioning above, and for the Runtime to eventually disconnect.

One last aside.  The Detach/(Re-)Attach method that @SayeedBinAbdullah mentions works well in version 6.10.x of Blue Prism.  Be aware, though, that the 'Detach' action goes away in version 7.x.  I have updated our standard 'Attach' action, and I am happy to show it to you, but it is not a perfect replacement for detaching and then re-attaching in sequence.

Good luck,

Red

[mariabarros]

Hi everyone! 😊 @grbanares @SayeedBinAbdullah @stepher 
Thank you so much for all the responses and suggestions!
At first, we thought the issue was memory-related as well, but after running several script tests, nothing critical showed up. We also confirmed that all application versions were matching.
After many attempts, lots of digging through ChatGPT, Copilot, and trial-and-error, we finally discovered that what seemed to interfere with Blue Prism's connection to the site were the actions inside the Navigate Stages, specifically the use of Activate Application for elements mapped using Windows 32 mode. Additionally, switching from Global Send Keys to Global Send Keys Event helped as well.
Personally, it still doesn’t make much sense to me, but it works! 😅
Hope this helps someone else facing a similar issue!