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

# verifyDoesNotExists

This is a pre-built Action located under the captured element. The functionality of this action in Avo Assure is to verify the specified object or element is not present on the current page of the application. The result is stored in the given dynamic variable for further use during test execution.

## **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 that a UI Element Does Not Exist**

In this example, we are explaining how to verify whether a specified UI element is not present on the screen.

* **Action**: verifyDoesNotExists
* **Input Value**: N/A
  * This action does not require any input value to check for the absence of the element.
* **Output Value**: {Status}
  * The verification result is stored in the **{Status}** dynamic variable, with the following possible values:
    * **True**: If the element does not exist on the screen.
    * **False**: If the element exists on the screen.
* **Logical Explanation**: The **verifyDoesNotExists** action identifies the captured object on the application interface and checks whether it is absent. The verification result (**True**) is stores in the **{Status}** variable.

<figure><img src="/files/5XpUDA8JBIkC34u3HjLM" 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/verifydoesnotexists.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.