> 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/support-resources/troubleshooting-guides/resolving-element-not-found-issue.md).

# Resolving Element Not Found Issue

<table><thead><tr><th>Problem</th><th valign="middle">Cause</th><th>Instructions to Resolve</th></tr></thead><tbody><tr><td><p>An <strong>element not found issue</strong> was observed in Avo client.</p><p> </p></td><td valign="middle"><ul><li>Re-capture the element in the application to ensure the latest properties are captured. </li><li>The <strong>element not found</strong> error occurred because the target element is dynamic, meaning its attributes (such as class, ID, or position in the DOM) change at runtime. As a result, the previously captured selector became invalid </li></ul></td><td><ul><li>Identify stable attributes: <br>Inspect the element and look for attributes that remain consistent, such as id, name, or data attributes.  </li><li>Use a reliable CSS selector: <br>Construct the selector using stable attributes in the format: <br>element tag[attribute name='attribute value']  <br>Example: div[class='button-container']  </li><li>Ensure the selector uniquely identifies the element without being overly dependent on the DOM structure. </li><li>Test the selector in browser developer tools to confirm it consistently identifies the correct element. </li><li>Replace the old selector with the improved one and re-run the test to verify the issue is resolved. </li></ul></td></tr></tbody></table>


---

# 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:

```
GET https://docs.avoautomation.com/avo-assure/support-resources/troubleshooting-guides/resolving-element-not-found-issue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
