> For the complete documentation index, see [llms.txt](https://help.listly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.listly.io/~/revisions/qSlWzjkSGWSbwiQWG3BZ/support/solutions-by-extraction-error-message/error-code-2.md).
# Error Code - AutoClickError
**AutoClickError**
This error occurs when setting up auto click, **if an incorrect Selector value is entered.**
### **✅ How to fix (when entering a CSS Selector)**
* After selecting the button element to click, **copy and paste the Selector value automatically generated in the PARTS window.**
You can easily obtain the Selector value after the Listly PARTS feature update.
* If you pasted the value this way and still get an error, it is possible that you selected **an area that is too small, or conversely too large,**relative to the element you want to click. → Try specifying a properly sized button area again.
* \[Note] Some sites may have a clickable area different from the visually visible element, so **the core element inside the button**choosing an area closer to is more reliable.
{% hint style="success" %}
**If it's still difficult to resolve after trying the guided methods,** [**hello@listly.io**](mailto:hello@listly.io)**please contact us at. We will diagnose the exact cause and help resolve it.**
{% endhint %}
---
# 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://help.listly.io/~/revisions/qSlWzjkSGWSbwiQWG3BZ/support/solutions-by-extraction-error-message/error-code-2.md?ask=&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.
