> 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/common-web-operations/verifyexists.md).

# verifyExists

This is a pre-built Action located under the captured element. The functionality of this action in Avo Assure is to verify the existence of the captured element, ensuring that the specified element is present and visible on the screen. The result is stored in the given dynamic variable for further use during test execution.

{% hint style="info" %}
**Note**: The **Verify Exists** action highlights the captured element on the AUT (Application Under Test) when executed.
{% endhint %}

## **Syntax**

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

| 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: Verifying the Existence of a UI Element

In this example, we are explaining how to verify whether a captured UI element exists on the screen.

* **Action**: verifyExists
* **Input Value**: N/A
  * This action does not require any input value. It checks the presence of the captured UI element within the application under test.
* **Output Value**: {Status}
  * The existence check result is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the UI element exists on the screen.
    * **False**: If the UI element does not exist on the screen.
* **Logical Explanation**: The **verifyExists** action does not require any input value. The action identifies the captured UI element within the application under test and determines whether it exists. The verification result (**True**) is stored in the **{Status}** dynamic variable.

<figure><img src="/files/d5KefE1HqvZdwj1932qo" 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/web/common-web-operations/verifyexists.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.