30-10-19 05:19 PM
28-04-20 08:27 PM
When performing Chrome spying/interation of a Process via Studio, the Process is run via the local Resource. The local Resource would initially open the connection and occupy it, and that local Resource would then hold on to Chrome via that connection. If you do not perform a reboot of the Resource machine after your local resource get connected, your next attempt to run the Process from Control Room on the same machine will cause a failure, as the connection had already been opened and occupied by the local Resource, a new connection to Chrome from control room cannot then be initiated.
We have a support center article to describe the issue and solution here:
https://portal.blueprism.com/customer-support/support-center#/path/Automation-Design/Application-Integration/Chrome/1319712802/Why-is-my-Process-no-longer-able-to-spy-or-interact-with-Chrome-Browser.h...
Hope this helps.
06-12-20 11:35 PM
07-12-20 06:51 PM
09-12-20 10:38 AM
13-12-22 08:20 AM