Managing unexpected pop-ups
- Updated: 2024/03/11
Managing unexpected pop-ups
Any window that is external to the target application is considered a pop-up. For example, if you are using the Google Chrome browser, a Microsoft Windows Update notification is considered a pop-up.
System pop-ups such as anti-virus alerts, Windows update notifications, or notifications from other applications (such as Teams) might interrupt and even stop bot execution. With regular error handling logic, it can be difficult to block these pop-ups during bot runtime. Resilient automation can detect and triage these pop-ups to ensure a seamless bot execution.
SAP and HTML are the currently supported technologies.
The following diagram shows how a resilient and non-resilient bot handles pop-ups:
Supported packages
The handle unexpected pop-ups functionality is currently supported
for the following packages:
- Image Recognition (version 3.15.2 or later)
- Mouse (version 2.14..0 or later)
- OCR (version 2.12.1 or later)
- Recorder (version 2.11.5 or later)
- Screen (version 2.9.2 or later)
Limitations for handling pop-ups
The automation might fail if the system is unable to handle pop-ups in the following
scenarios:
- The pop-up is from an application that is running with administrator
privileges.Note: As a workaround, you can run the automation with administrator privileges by selecting the Run with administrative privileges check box in the Run bot now window.
- The pop-up application has any of the defensive programming such as pop-up should not be minimized or cannot change its z-order.
- Commands cannot handle the pop-ups that contain one of the following
options:
- Currently active window - the window that is active when the bot run starts.
- Desktop window - the default window or space behind all the open windows.
- Screen - the visible screen.