19-11-21 10:01 AM
19-11-21 01:49 PM
19-11-21 03:08 PM
Hi Both
There's a relatively easy Blue Prism way, and a more complex Group Policy way.
Blue Prism way
- at the completion of a process do not use a Terminate step, instead use SEND KEY EVENTS with "<{CTRL}{W}>{CTRL}" to close the window. This drastically reduces the chances of getting the restore pages error on relaunch. (For extra safety you can follow that with a short wait, then a Terminate, inside a block to catch the errors)
- at the start of a process use a 'Read Process Working Set' to check for any instances of 'msedge' that are running. If any are running then call 'Kill Process' to terminate them. Note that this WILL cause the problem with restore pages to appear
- when you first open Edge on your launch stage, wait a few seconds, then use CTRL+W as above to do a gentle close. Wait a few more seconds then launch again. As the most recent close was a gentle one, the browser will not show the restore pages prompt.
Group Policy way (untested)
Older versions of Edge would allow you to suppress the restore pages prompt, originally with a setting, then later with a registry key. Unfortunately both of these were depreciated by Microsoft.
The most recent advice I have seen for how to suppress this is to use a Group Policy setting, see the final part of this article: https://www.thewindowsclub.com/disable-restore-pages-notification-in-edge-browser
22-11-21 08:25 AM
23-11-21 03:43 PM
24-11-21 08:32 AM
24-11-21 10:38 AM
24-11-21 11:00 AM
24-11-21 11:13 AM
Description of change |
Reference |
---|---|
An intermittent issue resulting in a Browser extension was not detected error that prevented elements from being spied no longer occurs when attempting to launch a Chrome, Edge, or Firefox browser via the Application Modeller. The error occurred either in Studio or when running an automation, in the following scenarios:
|
24-11-21 11:27 AM