# Report Bugs

Have you encountered an issue with Avonni Dynamic Components? We're here to help! This page explains how to report bugs effectively so we can resolve them quickly.

***

## Before Reporting a Bug

Before submitting a bug report, please try the following:

1. **Review the** [**Troubleshooting & FAQs section**](/dynamic-components/resources/troubleshooting-and-faq.md) - Most common issues have documented solutions
2. **Check the Documentation:** Review [**Release Notes Page**](broken://spaces/JU6zQrEzmfEcUVL9Ocs7/pages/C5JggvNN4TQZrcHJCE8C) to ensure you're using the component correctly and that the behavior isn't expected. If not using the latest version, please update to it.
3. **Search the Community:** Check [**our Trailblazer Community Group**](https://trailhead.salesforce.com/trailblazer-community/groups/0F9KX000000iFxO0AU?tab=discussion\&sort=LAST_MODIFIED_DATE_DESC) to see if others have encountered the same issue and found a solution or workaround.
4. **Isolate the Issue:** Reproduce the bug in a *minimal, isolated environment*. Create a new, simple Dynamic Component with *only* the components necessary to demonstrate the problem. This helps us pinpoint the cause.
5. **Clear Browser Cache**: Clear your browser cache and cookies.
6. **Try on another browser**: Reproduce the issue on a different browser.

***

## How to Report a Bug

If you've gone through the troubleshooting steps and still encounter the issue, please report it by emailing us at [`support_dc@avonni.app`](mailto:support_dc@avonni.app). Include the following information in your report:

* **Subject Line:** Use a clear and concise subject line, such as: `[Bug Report] Data Table - Filter Not Working with Reactive Query`
* **Avonni Dynamic Components Version:** Specify the *exact* version number of the Avonni Dynamic Components package you are using. You can find this in Salesforce Setup > Installed Packages.
* **Component(s) Involved:** List the specific Avonni components involved in the issue (e.g., Data Table, Button, Query Data Source).
* **Steps to Reproduce:** Provide *detailed*, step-by-step instructions for reproducing the bug. Be as specific as possible. Include:
  * The exact configuration of the components involved.
  * Any relevant data source settings (queries, filters, etc.).
  * The particular actions a user takes to trigger the bug.
  * The *expected* behavior.
  * The *actual* (incorrect) behavior.
* **Screenshots/Videos:** Include screenshots or, even better, a short screen recording (e.g., Loom or Screencastify) to visually demonstrate the issue.
* **Error Messages:** If you see any error messages, include the *full text* of the message and any associated error codes.
* **Console Errors:** Include any errors from your browser's developer console (usually accessed by pressing F12).

***

### What to Expect After Reporting

1. **Acknowledgement:** We'll acknowledge receipt of your bug report within 2 business days.
2. **Investigation:** Our team will investigate the issue and attempt to reproduce it.
3. **Updates:** We'll keep you informed about the investigation's progress and any potential solutions.
4. **Resolution:** We'll address the bug in a future release of Avonni Dynamic Components. If possible, we may provide workarounds in the meantime.

Thank you for helping us improve Avonni Dynamic Components

***

## **Community Support While You Wait**

While our team investigates your bug report, you might find immediate help or workarounds in [**our Trailblazer Community Group**](https://trailhead.salesforce.com/trailblazer-community/groups/0F9KX000000iFxO0AU?tab=discussion\&sort=LAST_MODIFIED_DATE_DESC):

**Quick workarounds:** Other users may have encountered similar issues and found temporary solutions

**Confirmation from peers:** See if others are experiencing the same behavior, which helps validate the issue

**Alternative approaches:** Community members often suggest different ways to achieve your goal while avoiding the bug

**Updates and discussion:** Once we identify a fix, we often share updates in the community

Many bugs get unofficial workarounds from the community before the official fix is released. Even if you've submitted a formal bug report, posting about it in the community can help you move forward faster and help others who might encounter the same issue.

[**Join the Community**](https://trailhead.salesforce.com/trailblazer-community/groups/0F9KX000000iFxO0AU?tab=discussion\&sort=LAST_MODIFIED_DATE_DESC)


---

# Agent Instructions: 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.avonnicomponents.com/dynamic-components/resources/report-bugs.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.