Processes with MS Edge get terminated due to 'not connected' error

[BramVerbueken]

Hi all,

Is there anyone that has encountered the same issue? 

It is no longer possible to launch an application on MS Edge browser.

After the Navigate stage activity 'Launch' the robot goes to a wait stage to check if an element exists (e.g. username field) to verify it the browser is correctly launched.

But when going into the wait stage, an error message appears stating 'Internal: AMI error occurred in Wait stage 'fieldname' on page 'Launch' - Not Connected. 
Tried to add the attach actions (check if connected, and attach to application if needed) between the launch action and the wait stage. This has no effect. After the navigation step 'launch' the 'connected check' returns false. 
Because it returns false, the robot attaches to the application and continues going to the wait stage. The same error message pops up during the wait stage.

The MS Edge version used is 104.0.1293.47I

Thanks!

------------------------------
Bram Verbueken
Co-owner
BRobots
Europe/Brussels
------------------------------

[MattFry]

Hey Bram,
Our team seemed to have a similar issue last year when we were on 6.10.1, my memory is fuzzy on the specifics of the exact exception we were getting, but we were having to put a 10 second static wait after the launch stage before attaching or using a wait stage.

------------------------------
Matt Fry
RPA Developer
Huntington National Bank
America/New_York
------------------------------

[ManpreetKaur1]

Hi @BramVerbueken,

We also faced the similar issue and in order to resolve the issue, we used to perform below steps:

1.  Launch the application using Navigate stage
2. Add a static wait of 10s or more (depending on the slowness of the application)
3. Attach the application using windows title (or any other way, which you feel like)
4. Perform the next steps​

The attach won't work immediately launching the application as it requires time to launch. Hence, static wait is the only option which can be made as Environment Variable for better controlling

------------------------------
Manpreet Kaur
Manager
Deloitte
------------------------------

[BramVerbueken]

Thanks Matt!

------------------------------
Bram Verbueken
Co-owner
BRobots
Europe/Brussels
------------------------------

[BramVerbueken]

Thanks Manpreet!

------------------------------
Bram Verbueken
Co-owner
BRobots
Europe/Brussels
------------------------------

[PvD_SE]

Môgge Bram,

After encountering the same problem, but noticing a speed difference between different VDI's, we decided to not be greedy with the extra static delay and put in an extra 30 seconds rather than the 10 seconds that sometimes worked. We start Edge only at the beginning of the process, so some extra time here does no harm to the overall performance. If you stop and start Edge all the time, eg. after each Q-item, you want to be more picky about using longer static waits.

------------------------------
Happy coding!
---------------
Paul
Sweden
------------------------------

[MitchBaker]

Hi Bram,

We had this issue too and to resolve we turned off these settings in Edge:


Hope this helps

------------------------------
Mitch Baker
Senior Automation Developer
Imperial College Healthcare NHS Trust
------------------------------

[BramVerbueken]

Thank you!

------------------------------
Bram Verbueken
Co-owner
BRobots
Europe/Brussels
------------------------------

[BramVerbueken]

Thank you!

------------------------------
Bram Verbueken
Co-owner
BRobots
Europe/Brussels
------------------------------

[KellyFarquhar]

You can use the wait for Process Window action rather than a static wait,  That way you can move onto the attach as soon as the window is found rather than always having to wait x seconds

------------------------------
Kelly Farquhar
Senior Blue Prism Developer
The Very Group
Europe/London
------------------------------