---
version: "2026.1.0"
language: "en"
---
# Handle Web Alert

The **Handle Web Alert** building block handles an alert popup in an open browser window. This block only works with browser windows that were previously opened using the **Start Web Browser** block (or their child windows).

Fully expanded, the **Handle Web Alert**block shows the following properties:  
![image-20260205-135332.png](https://docs.leapwork.com/__attachments/a_5de59e6c9c8b3a46e5512c56f6e2f6a22c87c6e4ec2a94c884e75dbfd8c55a1a/image-20260205-135332.png?cb=995ea459424a386347985ade2cea0f82)

**Note:** The screenshot on this page uses the **Elegance Design** , introduced in **2025.3**. If you are using an earlier version, your layout may look different.

## Quick-start

1. Drag **Handle Web Alert** onto the canvas.

2. Connect the block in the flow and optionally specify **Action**. Optionally, you can adjust other parameters if needed.

3. Run the flow when it's ready.

## Building block parameters

Parameters  
* **Block header** : The green input connector triggers the block to start executing. The green output connector triggers when the selected action (for example accepting the alert) has been completed. You can rename the block by double-clicking the header text and typing a new title.

* **Action** : Selects what to do with the alert popup. Options are **Accept** or **Dismiss** .

* **Text value** : Contains any text shown in the alert popup. In some browser versions, the alert text may not be delivered correctly, and this value can be blank.

* **Default timeout** : If the checkbox is not selected, the timeout is **10 seconds** . If the checkbox is selected, the **Default timeout** value from the flow settings applies.

* **Timeout** : The maximum time spent performing the selected action before giving up. This is separate from the case **global timeout** in **Settings** , which can cancel a run if the whole case exceeds it.

* **Browser window**: Makes the block use a specific browser window. Multiple browser windows are not supported by Selenium Grid or external cloud providers such as Sauce Labs and BrowserStack.

## Resources

|                                                **Topic**                                                |                                                  **Description**                                                  |
|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
| [Flows FAQ](https://docs.leapwork.com/faq/latest/leapwork-flow-faq/flows-faq.md)                                                 | Common questions about creating, running, and managing flows in Leapwork.                                         |
| [Flows Troubleshooting](https://docs.leapwork.com/troubleshooting/latest/leapwork-flow-troubleshooting/flows-troubleshooting.md) | Guidelines and solutions for identifying and fixing issues that occur when building or running flows in Leapwork. |