> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/experience-cloud/help/how-do-i-report-bugs.md).

# How do I report bugs?

Have you encountered a bug? Find out how to provide all the essential information for speedy resolution.

If you encounter a bug, please report it through the chat feature in the bottom right corner of your screen or by emailing <experiencecomponents@avonni.app>. For faster assistance, include details about how and when the bug occurred.

## What information should I share?

To help *us* help *you* as efficiently as possible, please be sure to send us all the relevant details:

* Please mention if your support request relates to a specific screen component.
* Please describe your steps, what happens when you take those steps, and what you expect to happen instead.
* If you run into an error message, please pass along the error message in full.
* Can you send us a screenshot to show us what you're seeing? Or, can you send us a short video showing us the steps you are taking? These are extremely helpful!
* For a quicker resolution, consider [allowing us access to your Salesforce Org](https://help.salesforce.com/s/articleView?id=000384334\&type=1). This enables us to provide the most effective support for your issue.


---

# 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://docs.avonnicomponents.com/experience-cloud/help/how-do-i-report-bugs.md?ask=<question>&goal=<user_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.
