topic Its not about the element… in Product Forum

Chrome Browser-Running from control room

Paul.Curran — Wed, 03 Oct 2018 18:44:00 GMT

I'm using BP 6.3 and Chrome to access an online portal and download an excel file. I've been able to successfully spy the portal, navigate around same and download the excel. I've stepped through/over the logic multiple times and it works really well. I launch Chrome through a navigate stage with the URL for the portal then my next action is to wait for one of the elements on the portal to exist before moving onwards through the process. However when I incorporate the logic in my process and run from control room my process throws an error at the next element post launch, the next stage is a wait stage to ensure a field 'username' exists. This times out every time despite being spied correctly when I access App Modeller. See attached how I've spied this field. Any ideas?

Experiencing the same issue.

AlesiaDzerhacho — Fri, 26 Oct 2018 13:24:00 GMT

Experiencing the same issue.

Maybe try excluding the…

John__Carter — Fri, 26 Oct 2018 21:44:00 GMT

Maybe try excluding the wildcard attribute altogether.

Yeah really having some…

coreydrees — Fri, 14 Dec 2018 03:48:00 GMT

Yeah really having some weird symptoms when running Chrome from the control room

Hello, did anyone solve this?

fkargman — Tue, 08 Jan 2019 22:17:00 GMT

Hello, did anyone solve this?

How many pages do you need…

AmiBarrett — Tue, 08 Jan 2019 22:50:00 GMT

How many pages do you need to keep open simultaneously? In most cases, you can turn off the URL check entirely.

Its not about the element…

fkargman — Wed, 09 Jan 2019 23:15:00 GMT

Its not about the element attributes cheked i think... For instance i only check the web path (that dosnt change) in a chrome button element and when i run the process in debug mode it works fine. But when i run the process via control room, the wait stage that checks for that element to exist, fails and goes to timeout. Its not about time waiting either because i tried the same thing with a 10 second sleep before the wait stage (just to check its no about the control room running too fast) and it still fails. Hope anyone can solve this problem... Im contacting bp support anyway

Hi, Same problem here. Did…

CarlaFreitas — Fri, 08 Feb 2019 17:03:00 GMT

Hi, Same problem here. Did anyone solve?

Hi, Same problem here. Did…

CarlaFreitas — Fri, 08 Feb 2019 17:03:00 GMT

Hi, Same problem here. Did anyone solve?

Same issue. @fkargman Got it…

MadliAllikmäe — Tue, 12 Mar 2019 13:10:00 GMT

Same issue. @fkargman Got it fixed?

RE: Same issue. @fkargman Got it…

ZdravkoBotushan — Thu, 30 Apr 2020 08:34:00 GMT

Hey guys. I'm having the same issues. Process works great in Debug mode. When I run it from Control Room, it opens the browser and terminates.

The logs show: ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Attach' on page 'Attach' - Target application could not be identified.

Any ideas?

------------------------------
Zdravko Botushanov
Senior RPA Consultant
Human+
Europe/Sofia
------------------------------

RE: Same issue. @fkargman Got it…

ZdravkoBotushan — Thu, 30 Apr 2020 08:35:00 GMT

RE: Same issue. @fkargman Got it…

_Amlansahoo — Thu, 30 Apr 2020 10:36:00 GMT

HI Zravko,

If you are debugging and then trying to tun from control room it might night work. Because it's a know issue in chrome you can can not run 2 instances of chrome at the same time. Restart your server and try running either debug or from control room it will work.
I guess chrome started working better after 6.4.2 on wards so try it. I am running a process from last one year in Production without any issue in 6.4.2.

------------------------------
Amlan Sahoo
RPA Consultant
Equinix
------------------------------

RE: Same issue. @fkargman Got it…

ZdravkoBotushan — Thu, 30 Apr 2020 13:12:00 GMT

Hi Amla,

Unfortunately, I did try restarting the machine, closing all Chrome instances beforehand etc. Everything works 100 % in debug mode, but in Control Room, it only opens the browser and crashes with ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Attach' on page 'Attach' - Target application could not be identified.

------------------------------
Zdravko Botushanov
Senior RPA Consultant
Human+
Europe/Sofia
------------------------------

RE: Same issue. @fkargman Got it…

_Amlansahoo — Thu, 30 Apr 2020 17:14:00 GMT

It's weird. Raise a ticket with Blue Prism support team. They may help you with the same.

------------------------------
Amlan Sahoo
RPA Consultant
Equinix
------------------------------