topic Re: Browser extension not detected in Product Forum

Browser extension not detected

Sushmitha.C — Mon, 27 May 2024 07:37:20 GMT

Hi,

While launching a site using chrome encountering below error in Navigate stage.

ERROR: System Exception : Failed to Launch Portal: Failed to perform step 1 in Navigate Stage 'Launch' on page 'Launch' - The browser extension was not detected, please check that it has been installed and enabled. For more information, see the browser extension user guide.

https://bpdocs.blueprism.com/bp-6-10/en-us/Guides/chrome-firefox/chrome-firefox.htm

The issue happens intermittenly.

Version of BP is 6.10.3 and browser extenstion is 6.10.3. Timeout is also in place.

Any idea what may be causing this?

Re: Browser extension not detected

rabbanir — Tue, 28 May 2024 10:42:25 GMT

Hi Sushmitha.C,

I don't have a resolution but I'm just replying to say we get a similar issue when launching edge intermittently. I've noticed though that the exception saying the browser extension was not detected only occurs when running through the studio. When this issue happens intermittently on a schedule the exception is different:
ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Launch ESR Application' on page 'Launch' - Process with an Id of -1 is not running.

From what I understand the launch action also attaches to the application, I wonder if it's trying to attach too fast? there doesn't seem to be a way to delay the attach within the launch though, or maybe I am wrong.

Re: Browser extension not detected

Chakkravarthi_PR — Tue, 28 May 2024 12:01:31 GMT

Hi,

Ensure that the Blue Prism browser extension is properly installed and enabled in Chrome. Sometimes, updates or changes to the browser can disable extensions.
Chrome updates can sometimes affect extensions. Make sure Chrome is up to date, and if there was a recent update, check if the issue started occurring afterward.
Ensure that the extension has the necessary permissions. Go to Chrome's extensions page (chrome://extensions/), find the Blue Prism extension, and check its permissions.
Although you mentioned that a timeout is in place, you might need to increase the timeout period to give the extension more time to initialize.
As a last resort, try uninstalling and then reinstalling the Blue Prism extension.

Re: Browser extension not detected

expertcr — Tue, 28 May 2024 12:30:54 GMT

Take a look at the following KB article: BPE error "The browser extension was not detected" when attempting to launch a browser based (Chrome, Firefox or Edge Chromium) application

Re: Browser extension not detected

faheemsd — Tue, 28 May 2024 14:09:29 GMT

Dear @Sushmitha.C

Is it happening in run time machines or your development machines?

Re: Browser extension not detected

michaeloneil — Wed, 29 May 2024 11:21:57 GMT

We recently upgraded our environments to version 7.3 of blueprism and had some similar issues with the browser extension. Firstly just be sure the extension you have is the same version of the application, secondly make sure the browser is still installed on the browser. We had an issue where if the extension was installed through the BP installer it would disappear a few hours later due to group policies removing it, we resolved this by installing it directly from microsoft Blue Prism 7.3 Browser Extension - Microsoft Edge Addons

Finally even after resolving the issues with the xtension we still got some cases where the launch threw the same error youre getting. But this was a simple change in the object to catch the error on launch then do an attach and then carry on. We couldnt figure this out but for some reason the launch would sometimes throw this error and only on some of our processes not all of them, but by just doing an attach after catching the error we worked round it.

Hope this helps.

Re: Browser extension not detected

WarrenBowman — Wed, 15 Jan 2025 15:10:02 GMT

What is the current Browser extension for chrome.exe?

Re: Browser extension not detected

Sushmitha.C — Sun, 17 Aug 2025 11:14:40 GMT

This was issue with chrome version itself, bug in the version. It got resolved after updating the chrome.

Re: Browser extension not detected

WarrenBowman — Fri, 22 Aug 2025 20:40:16 GMT

Working with a few other developers it was determined that the inconsistent error could be ignored via the use of a recovery followed by a wait stage of up to 5 minutes looking for the expected page. In this case we're waiting for the Fidelity Sign On page. This work around is successful most of the time but not all the time, sometimes it still fails.

Re: Browser extension not detected

simone.tomaCNH — Thu, 28 Aug 2025 08:28:25 GMT

Hi,

With version 7.1.2, even though the extension was installed, it was not recognized because it was still loading. This problem can be solved by increasing the standard timeout of the Messaging Host (for example, from 10 to 150). In our case, this solved the problem.

Simone

Re: Browser extension not detected

expertcr — Thu, 28 Aug 2025 15:20:16 GMT

I recommend that everyone take a look at the following KB Article "What are the key considerations when working with Modern Browser Automations on BP version 7.X?"

This is a great article that helps prevent that issue and other related issues when working with modern browsers. It is something we should use as a best practice in our automation to make them more resilient.