BP not Attached after Launch of Edge Browser Application

[KirstyWebb]

We have recently noticed that when in debug mode the launch actions we have created for Edge Browser no longer automatically attach to the instance of the browser.

to combat when stepping through after the launch stage we are having to step through our attach action to enabling spying and to continue stepping through.

Is this something anyone else has experienced? any advice on how to combat this would be great

------------------------------
Kirsty Webb
Automation Service & Operations Manager
The Co-op
Europe/London
------------------------------

[Neel1]

Hello Kirsty - are you getting any error when you are not able to attach post launch of Edge.
which version of BP and edge browser you are using?

------------------------------
Neeraj Kumar
Technical Architect
------------------------------

[PvD_SE]

Hi Kirsty,

Notably, some actions do not work properly in debug mode. The ones we use for Edge and Chrome have to be Run rather than Stepped for them to work.

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

[KirstyWebb]

hello - we don't get the error when attaching its after we use the launch action the next stage be it wait or navigation stage fails because the object isn't connected but this should be as it within the same action as the launch step, we are then having to attach to be able to continue working the action,

we are on v6.8 of BP and v107 of Microsoft edge

thanks for trying to help 🙂

------------------------------
Kirsty Webb
Robotic Process Automation Analyst
The Co-op
Europe/London
------------------------------

[KirstyWebb]

Hello - all of our actions have always worked in debug mode we've never been not able to step through without this work around of attaching at the beginning of each action (even in the object that launches the application) so it's unusual for us, especially as nothing had changed (that we were aware of) when we started seeing this occur
Thanks

------------------------------
Kirsty Webb
Robotic Process Automation Analyst
The Co-op
Europe/London
------------------------------

[NileshJadhavBP]

Hi @Kirsty Webb,

​I had faced the same issue with previous version, We had added one action to kill msedge.exe before launching the Edge in the process.

Select business object - Utility - Environment & Kill process as action to kill the process.

I know this is not end solution. However, it's just work around for the issue​.

Please check and let me know if its work to or not.

If my answer is helpful for you, please vote for it to be the "Best Answer".



------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

[KellyFarquhar]

I've seen this when we use edge in IE Compatibility, It seems to take a bit longer to fully launch, I added in a wait for process window stage before using a check connected and then an attach if needed but not found a way that it will launch attached.

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

[KirstyWebb]

Thanks Nilesh, we do already have those steps in place and are still experiencing the issue. The only work around is to attach after launch which is ok for now, just glad to see that this seems to be an issue that others face and not just us. i'll raise it with Blue Prism support 🙂

------------------------------
Kirsty Webb
Robotic Process Automation Analyst
The Co-op
Europe/London
------------------------------

[john.schreier]

Hi, Kirsty:

We're in the process of converting to Blue Prism from Kofax RPA at my work, so this might be my inexperience at play here, but we're seeing a similar error.

Most of the time (but not every time) I try to launch the Microsoft Edge browser, I receive the following error: "Internal : Failed to perform step 1 in Navigate Stage 'Open Browser' on page 'Open Browser' - The query did not match the window title provided, please try again." The strange thing about it is that the browser window always opens, regardless of whether the error message pops up.

Because this is a root-level application spied by Application Modeler, I don't have the ability to modify it nearly to the level I can for a child.

Any suggestions? I really appreciate any help that anyone can provide here.

Thanks,
-John

------------------------------
John Schreier
------------------------------

[Mukeshh_k]

Hi @John Schreier  is it launch action that is failing or the attach action ? and if its launch action are you killing the browser before each retry ? - I would usually leverage Utility Environment - Start process action to launch, wait 5 seconds and attach it via Business Object


If Launch fails from this block I would kill edge by Taskkill and retry it:


If its attach which is failing - Keep the windows title as wildcard * : something like this and check if its highlighting the outer window- if the window titles are changing and if at least some part of window title is common in each window better to use that as wildcard  :

------------------------------
Kindly up vote this as "Best Answer" if it adds value or resolves your query in anyway possible, happy to help.

Regards,

Mukesh Kumar - Senior Automation Developer

NHS, England, United Kingdom, GB
------------------------------