> 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/verify-exists.md).

# Verify Exists

This is a pre-built Action located under the captured **Grid Element**. The functionality of this Action in Avo Assure is to verify whether the captured grid is present on the current screen and store the verification result in a dynamic variable.

## Syntax

**Input Value**: `N/A`

{% hint style="info" %}
**Note**: This action does not require an input value.
{% endhint %}

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

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

| Argument                                 | Description                                                                                                                                           |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable stores the verification result as **True** or **False**, indicating whether the captured grid is present on the current screen. |
| <p>\<Dynamic Variable><br>(Optional)</p> | This dynamic variable stores the execution result as **Ture** or **False**.                                                                           |

### **Example: Verifying the Presence of a Grid**

In this example, we explain how to verify whether a captured grid exists on the current screen.

* **Action**: Verify Exists
* **Input Value**: N/A
  * This action does not require any input value.
  * The action checks whether the captured grid is present on the current screen.
* **Output Value**: {GridExists}
  * The verification result is stored in the **{GridExists}** dynamic variable with the following possible values:
    * **True**: If the captured grid is present on the current screen.
    * **False**: If the captured grid is not present, inaccessible, or not loaded.
* **Logical Explanation**: The **Verify Exists** action checks whether the captured grid is available on the current screen using its captured properties. If the grid is found, the action stores **True** in the **{GridExists}** variable.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FJJufqahtx0iM0ppPbGZV%2Funknown.png?alt=media&amp;token=e68e2ad0-eaf4-4ac8-9105-22f1b978530c" alt="" height="48" width="626">

#### Knowledge Bites

The following examples show different verification scenarios:

| Scenario                                      | Output Result |
| --------------------------------------------- | ------------- |
| Grid is displayed on the current screen       | True          |
| Grid is hidden or not loaded                  | False         |
| Grid is unavailable due to navigation changes | False         |


---

# 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/verify-exists.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.