13-01-23 05:27 AM
10-07-24 10:27 AM
Yes, this is a reported issue with Blue Prism and Chrome browser extension using Manifest V3. Here's what you might be facing:
Here are some solutions you can try:
Check Blue Prism Community: Several users have reported this issue on the Blue Prism community forums. Search for "The browser extension was not detected" to see if there are any updates or workarounds mentioned.
Upgrade Blue Prism (if possible): Blue Prism versions 7.2 and above (for version 7) and 6.10.6 and above (for version 6) include the Browser Automation Agent by default. This agent offers improved browser interaction compared to the Manifest V3 extension. Upgrading Blue Prism might resolve the issue if compatible with your system.
Use the Manifest V2 Impact Assessment Utility: Blue Prism offers a utility to identify if your automations rely on features not supported by Manifest V3 extensions. This can help you plan your upgrade strategy or identify areas needing adjustments.
Contact Blue Prism Support: If none of the above solutions work, consider contacting Blue Prism support for further assistance. They might have additional insights or recommendations specific to your environment.
a week ago - last edited a week ago
Has there been any further update with this issue? We're currently running 6.10.5 and have noticed an uptick in instances of this over the past month or so. As other contributors have discussed, all suggestions (Fixed Port, Reboots, Increased throttling) have - at best - mixed success rates, and the issue is still occurring frequently enough for this to become a more significant issue.
Just to clarify, we're having this issue with both Edge and Chrome-based automations.