> 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/flow/tutorials/reactive-query-tutorials/troubleshooting.md).

# Troubleshooting

## **Troubleshooting Your Reactive Query Formulas**

Have trouble getting your reactive query formula to work correctly? Here's a breakdown of how to troubleshoot and achieve the desired results:

## **Step 1: Visualize the Output**

Before conducting direct SOQL testing, use a Display Text element in your flow to reveal the exact value your formula produces. This will provide a crucial visual check.

Ask yourself: "Does this output make sense as something that could go after the `WHERE` clause in a SOQL query?"

For example, if your Display Text shows something like `'Name = 'John Doe' AND Account.Industry = 'Technology'`, you're on the right track! If it shows something jumbled or nonsensical, you'll need to revisit your formula.

This "sneak peek" helps you catch potential issues early on.

<figure><img src="/files/LjxZD7B5tSc4aHwCrBEX" alt=""><figcaption></figcaption></figure>

## **Step 2: Direct SOQL Testing**

The most reliable way to validate your formula is to test it directly within a SOQL query. Think of your formula as the part that comes **after the `WHERE` clause** in a SOQL query (like the highlighted portion in the example below).

<figure><img src="/files/BdsQ8mkNyC88CdmM3HNg" alt=""><figcaption></figcaption></figure>

### **Interpreting the Results**

* **Success!** If your SOQL query returns the expected results, congratulations! Your formula is likely correct.
* **Error?** If Salesforce throws an error message, it means there's something wrong with the syntax or structure of your query. Carefully review your formula for any mistakes.

### **Example**

Let's say your formula looks like this:

```
"Name LIKE '%"&{!NameInput.value}&"%' AND Account.Industry = '"&{!IndustryCombobox.value}&"'" 
```

To use this in a SOQL query, you'd modify it to:

SQL

```
Name LIKE '%Acme%' AND Account.Industry = 'Technology'
```

Use code with caution.

***

## **Important Considerations**

* If your SOQL query with the modified formula throws an error, your original formula might have a syntax issue.
* Ensure the values you use in your test SOQL query are valid and exist in your Salesforce org.

By following these steps, you can effectively pinpoint and resolve issues with your reactive query formulas.

***

## **Still Stuck?**

If your SOQL query works fine and the Display Text output looks correct, but your Avonni component filters still don't behave as expected, a more nuanced issue might be at play. In this case, please don't hesitate to [contact our support team](/flow/help/support-and-troubleshooting.md) for assistance. We're here to help!


---

# 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://docs.avonnicomponents.com/flow/tutorials/reactive-query-tutorials/troubleshooting.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.
