25-07-23 02:34 PM
We are performing below steps
Is this a known issue in 7.2 ?
25-07-23 03:28 PM
Screenshots are always helpful.
But based on the little information you have provided, it appears to me that you may need to reinstall/repair the Blue Prism browser extension and then retry.
26-07-23 02:54 AM
Agree. There should only be one extension installed, reflecting your current BP version.
Also, in Edge settings turn off "Startup Boost", as recommended to us by BP support.
If that doesn't work, you might have to adjust the timeout settings in the automate.exe.config file in your Blue Prism installation directory. If you are uncomfortable doing so, open a support ticket and they will guide you through that process.
The default timeouts for launch and communication are, I believe, 2000ms and 3000ms respectively.
26-07-23 03:54 AM
I will also add retry logic on top of other suggestions mentioned by the other members.
Retry logic will check browser extension error or not, if it is browser extension it will kill the process and wait for 5 seconds and then launch again
I suggest to include the retry logic in process level
26-07-23 06:38 AM
Hi Sheela,
We've implemented the logic in the following thread which commendably decreased the browser extension issue.
01-08-23 02:56 PM
HI Sheela. I would recommend adding a wait or sleep stage (we use 10 sec) between killing a process and launching, again. This has dramatically decreased the browser errors we are getting when launching.
------------------------------
Melissa Nail
AVP, Automation Controller
BOKF, NA
America/Chicago
------------------------------