> 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/grid/wait-for-element-to-be-visible.md).

# Wait for Element to be Visible

This is a pre-built Action located under the captured **Grid Element**. The functionality of this Action in Avo Assure is to wait until the captured grid becomes visible on the current screen and store the execution result in a dynamic variable.

## Syntax

**Input Value**: N/A

{% hint style="info" %}
Note: The Action waits until the captured grid becomes visible or until the configured timeout period is reached .
{% endhint %}

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

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

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | Both dynamic variable stores the status as **True** or **False**. |

#### Example: Waiting for a Grid to Become Visible

In this example, we explain how to wait until the captured grid becomes visible on the current screen.

* **Action**: Wait for Element to be Visible
* **Input Value**: N/A
  * This Action does not require any input, Avo Assure waits for the captured grid to become visible.
* **Output Value**: {Status}
  * The execution status is stored in the **{Status}** dynamic variable.
    * **True**: If the captured grid becomes visible within the configured timeout period.
    * **False**: If the captured grid does not become visible within the configured timeout period .
* **Logical Explanation**: The **Wait for Element to be Visible** action checks whether the captured grid becomes visible on the current screen. The action continuously monitors the grid until it becomes visible or the configured timeout period is reached. If the grid becomes visible within the timeout period, the action stores **True** in the **{Status}** variable.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FikKbODaGcmlojokhP0rn%2Funknown.png?alt=media&amp;token=2bf1b088-2445-4e21-b8bd-0ecf17d6a003" alt="" height="47" width="626">


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/grid/wait-for-element-to-be-visible.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.