Attach Warning

[bridgetoneill]

Hi all,

We've had issues with Attach warnings since upgrading to Blue Prism 7.4.2.

An overview: sporadically, scheduled processes go into Warning status in Control Room when trying to attach to a Chrome instance. It primarily happens on the first attach after Chrome is launched. Once it goes into Warning it hangs there until we manually intervene.

I've seen this issue, or similar, mentioned a couple of times in these forums:
#https://community.blueprism.com/t5/Product-Forum/BP-V7-process-hangs-on-Attach-and-sticks-in-Warning-state/td-p/126059

#https://community.blueprism.com/t5/Product-Forum/Warning-when-attaching-to-browser-causes-process-to-hang/m-p/124111#M54255

What we've already tried:

• Increased the Browser Extension messaging host timeout in System Settings to 40 seconds
• Kill Chrome at the start of the process
• A throttle after Chrome is launched

What I'm going to try next:

• A throttle after the kill and before the launch

Given this has come up a few times before, has anyone got to a root cause or a fix?

Thanks,
Bridget

[OmegaRPA]

Hi Bridget, we've had this exact issue on 7.4.1 where it's only ever the first attach of a session! In our experience, there are a couple webapps that are affected more than others - those webapps being ones where some login/auth is taking place, and some redirects are happening in the browser.

Timeouts, messaging host timeout, and throttles and Edge kills made no difference to us.

We recently got a specfix from BP. I advise you reach out to John Pass of customer support and mention the specfix, as it has only recently been delivered (under 2 weeks ago).

But in that time since installing, we have had ZERO hangs on our machines, so I'd say it's done the job...

[bridgetoneill]

Hello,

The more I look into this, the more it seems to be a known issue that is likely to be fixed with v7.5.

Customer support have sent us these links that explain the problems with Chrome and Edge 140 which can cause BP to freeze and not proceed:

• [BPE] BPNGRPA-10051 - Wait stages executed against Chrome and Edge 140 can cause Blue Prism Enterprise to pause/freeze and not proceed to subsequent stages 
• Why do I have Browser Automation issues after updating to Chrome or Edge browser version 140? : 

I've also added your findings / fix to our ticket so fingers crossed we get either a patch or can upgrade to 7.5 as soon as possible. Sounds like I'll save myself the effort of the extra throttles - thanks for the heads up!

Thanks again,

Bridget

[OmegaRPA]

I wouldn't bank on 7.5 solving this. It seems that the issue isn't the famous Chromium140 issue(that affected UIA elements), but something else entirely.