> For the complete documentation index, see [llms.txt](https://airbotfarm.gitbook.io/airbot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://airbotfarm.gitbook.io/airbot/general/reporting-issues-and-bugs.md).

# Reporting Issues and Bugs

We strive to make AIRBOT as stable and effective as possible, but occasional issues or bugs may occur. If you encounter a problem, please let us know so it can be addressed promptly.

To report issues or bugs:

* **Raise a ticket in Discord** - You can raise a ticket by going to the #support channel and clicking the "Raise a ticket" button. Our support team will assist you.

When reporting bugs, provide as many details as possible, like wallet addresses used, parameter configurations, error messages, screenshots, etc. This helps our developers reproduce and pinpoint the problem faster.

Rest assured, our team actively monitors Discord tickets to quickly resolve any bugs or issues impacting the performance or functionality of Airbot. We appreciate you taking the time to report problems so we can continue improving the product.


---

# 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://airbotfarm.gitbook.io/airbot/general/reporting-issues-and-bugs.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.