Blue Prism 7.3 – Intermittent Chrome Browser Attachment Issue with Salesforce

[surajseetha]

Hi Team,

I'm facing an issue while attaching Blue Prism to the Chrome browser when automating Salesforce.

The first object successfully attaches to the Chrome browser and performs the required actions. However, when the second object attempts to attach to the same Chrome window on the same Salesforce page, the attachment fails.

Interestingly, the attachment starts working again only after I manually toggle the Blue Prism Chrome extension OFF and ON and refresh the page.

Environment Details:

• Blue Prism Version: 7.3

• Blue Prism Chrome Extension Version: 7.3

• Chrome Version: 156.0.8078.79

• Application: Salesforce

Authentication / Browser Launch Approach:

I'm using the Salesforce API to generate the access token through the JWT Bearer Token flow. The browser is launched using the Salesforce URL generated with the access token.

Troubleshooting Steps Already Tried:

1. Kept the Detach action in the first object and tested, but the issue persisted.

2. Removed the Detach action from the first object and tested, but the issue still persisted.

3. Verified the Blue Prism Native Messaging Host, and it shows as running.

Expected Behaviour:

Blue Prism should be able to attach to the same Chrome browser window from multiple objects without requiring the extension to be restarted or the page to be refreshed.

Actual Behaviour:

The first object attaches successfully, but the second object fails to attach to the same Chrome window. Toggling the extension OFF and ON and refreshing the page temporarily resolves the issue.

Has anyone experienced a similar issue with Blue Prism 7.3 and Chrome, particularly when automating Salesforce?

Could you please suggest any possible solutions or additional troubleshooting steps to resolve this issue?

Thanks in advance for your help.

[david.l.morris]

I have never automated Salesforce, so what I'm suggesting is generic for any web automation and is worth checking.

Look in Application Modeller at the Application Manager mode. As far as I'm aware, it has to be set to Embedded in order for multiple objects to attach to Chrome/Edge at the same time. If set to External, it will fail on the second attach. This does not apply to all application types but at least applies to browser mode objects. If it's already set to Embedded in all of the objects involved (such as the one that is failing to attach), then you have a different issue, but be sure to check each.

A couple of options:

1 - As I mentioned above, change to Embedded (in all objects involved).

2 - If you need external for some reason (I have no idea why that would be necessary here), then you could temporarily switch to some objects being Windows application when going through the Application Wizard, and that should work to attach with multiple objects, if I remember correctly.

(3) - This one is not related to the above info. Instead, I should also mention to check that you are attaching by Tab Name and not Window Title, which is something that changed with the move to Manifest Version 3 browser extensions. Basically in "Some Website - Blah Blah - Chrome", you need to use only the "Some Website" part. In Edge, it looks like "Some Website - Work - Microsoft Edge" which then changes to "Some Website". And of course you can put an asterisk at the end.