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

# Wait for Element to be Visible

This is a pre-built Action located under the **Custom** **Element.** The functionality of this action in Avo Assure to wait until the element is visible on the web page. Before making the step fail, this time to wait should be set in configuration settings using the **Timeout** property, and the result is stored in a dynamic variable.

### **Syntax**

**Input Value:**`<ObjectType>;<VisibleText(optional)>;<Index>;<abs(optional)>`

| Argument                            | Description                                                                                                               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Reqyired)</p>  | Specify the type of the object                                                                                            |
| <p>\<VisibleText><br>(Optional)</p> | Enter the visible text on the object                                                                                      |
| <p>\<Index><br>(Reqyired)</p>       | Provide the position of the element, which helps to identify the value based on the sequence in list . (starting from 0)​ |
| <p>\<abs><br>(Optional)</p>         | If the **abs** is provided, the action is performed with absolute identification using the **absolute X path**            |

{% hint style="warning" %}
**Note:** Set the Timeout property in the configuration settings within the Avo Assure client.

*To skip an optional input value, use an extra semicolon (;).*
{% endhint %}

**Output Value**

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

**Example**

**Waits for a button to become visible after login**

The **Wait for Element to be Visible** action takes the value from the Input Value column (e.g., **img;;0**) and waits for the element to appear on the screen. The result of the wait operation is stored in the **{Element}** variable, with the following possible values:

* **True** – if the element becomes visible within the timeout.
* **False** – if the element does not appear within the timeout.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FKpTUnGYKdtJqMyD2iyXD%2Fimage.png?alt=media&amp;token=1741f9f6-bfd8-4305-88e3-45201c72a196" 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 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/web/custom/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.