> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/generic/interrupt-operations/wait.md).

# Wait

This is a pre-built Action located under the **@Generic Element**. The functionality of this Action in Avo Assure is to pause the test execution for a specified number of seconds and then continue to the next step. The  status is stored in a dynamic variable.

## **Syntax**

**Input Value**: `<Time in Seconds>`&#x20;

{% hint style="info" %}
In Avo Assure, the Wait action is enhanced for web applications.

Earlier, users enter a wait time (for example, 5 seconds) in the Input Value field to handle loading delays. Now, Avo Assure automatically waits for elements to become clickable, visible, or ready. This removes the need for manual wait times and makes test execution smoother and more reliable.

**Note**: This enhancement currently applies only to web applications.
{% endhint %}

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Time in Seconds><br>(Required)</td><td>Provide the duration in seconds for which the test execution should wait before proceeding to the next step.</td><td></td></tr></tbody></table>

**Output Value:** `<Dynamic Variable>;<Dynamic Variable>(Optional)`&#x20;

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable> (Required);&#x3C;Dynamic Variable> (Optional) </td><td>Both dynamic variable stores the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### **Example:** Waiting Before Executing the Next Action

In this example, we explain how to use Wait action to delay the execution for a specific duration.

* **Action**: Wait
* **Input Value**: 5
  * The input value (**5**) specifies the number of seconds for which the execution must pause.
* **Output Value**: {Status}
  * Avo Assure stores the result of the wait action in the **{Status}** dynamic variable as **True** or **False**:
    * **Ture**: If the wait completes successfully.
    * **False**: If the wait is action is not work or empty input value.
* **Logical Explanation**: The **Wait** action fetches the value from the **Input Value** column (**5**). It pauses the test execution for **5 seconds** and then resumes the next step. After the pause completes, it stores the result as (True) in the **{Status}** variable. This ensures that elements load properly, background processes complete, and the system becomes ready for the next action.

<figure><img src="/files/OfrI4lB6YkCFHGkwT9g9" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/generic/interrupt-operations/wait.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.