---
title: Troubleshoot query pipeline rules
slug: '2088'
canonical_url: https://docs.coveo.com/en/2088/
collection: tune-relevance
source_format: adoc
---
# Troubleshoot query pipeline rules
If one or more [query pipeline](https://docs.coveo.com/en/180/) [rules](https://docs.coveo.com/en/236/) aren't behaving as you expect, you can find useful troubleshooting information in the execution report.
This report contains query evaluation details such as which [query pipeline features](https://docs.coveo.com/en/234/) were applied and in what order, what the final [query](https://docs.coveo.com/en/231/) sent to the [index](https://docs.coveo.com/en/204/) was, and so on.

## Access the execution report

> **Note**
>
> Google Chrome is the browser used for this tutorial.
> Although you can access the execution report using any browser you like, the process may differ.

. In the page where your search component is integrated, access the **Network** tab of the Google Chrome developer tools by either:
 ** Selecting F12.
 ** Right-clicking anywhere on the page, selecting the **Inspect** option, and selecting the **Network** tab.

![Access developer tools in Chrome](https://docs.coveo.com/en/assets/images/query-pipeline-in-dev-tools.gif)

. Type a query in the search box, and then select Enter or click the search button.
. Enable the debug mode by either:
 ** Adding `&debug=true` at the end of the current URL address.

![debugTrueExample](https://docs.coveo.com/en/assets/images/tune-relevance/debug-true.png)

 ** Selecting and holding Alt (Windows) or Option (Mac) and double-clicking any search result box.
At the upper right of the panel you just opened, make sure the **Enable query debug** option is selected.
You can then close this panel by selecting Esc.

![QueryDebugExample](https://docs.coveo.com/en/assets/images/tune-relevance/query-debug.png)
. Return to the developer tools panel you opened in step 1.
. In the **Name** column of the network request table, select the HTTP request which corresponds to the query you just submitted.
This should be the latest POST or GET request to `+https://platform.cloud.coveo.com/rest/search+` or `+https://platform.cloud.coveo.com/rest/search/v2+`.

![NameSectionExample](https://docs.coveo.com/en/assets/images/tune-relevance/name-section.png)

. Select the **Preview** tab.
You should now see the query response body.
. Expand the `executionReport` property.
. Expand the `children` property.
You should now be able to visualize the whole path your query took before the results were returned to [search interface](https://docs.coveo.com/en/2741/).

![children-subsectionExample](https://docs.coveo.com/en/assets/images/tune-relevance/execution-report.gif)

> **Note**
>
> In the execution report, some query pipeline features have different names than in the [Coveo Administration Console](https://docs.coveo.com/en/183/) (see [Query pipeline features](https://docs.coveo.com/en/1450#query-pipeline-features)).

**Example**

. In a new query pipeline named `My Pipeline`, you create the following **Filters** rule:

Add `@source=="movie"` to the [advanced query expression (`aq`)](https://docs.coveo.com/en/175/).

. In the same pipeline, you create the following **Thesaurus** rule:

Replace `The Lord of the Rings` in the current query by `The Fellowship of the Ring` if the advanced query is `@source=="movie"`.

. To test your changes in the query pipeline, you send this query to the search interface: `The Lord of the Rings`.
You realize that rule 2.
was never applied.
. To understand what went wrong with the query going through `My Pipeline`, you access the execution report, which gives you the following information:

![Troubleshooting query example | Coveo](https://docs.coveo.com/en/assets/images/tune-relevance/troubleshooting-query-example.png)

As the items in the execution report **children** subsection appear in the actual order they were executed on the pipeline, you see that the **Thesaurus** rule executes _before_ the **Filters** rule.
Because of this, the advanced query (`aq`) remains undefined until later in the execution when the **Filters** rule is executed, therefore failing to satisfy your **Thesaurus** rule (see [Order of execution of query pipeline features](https://docs.coveo.com/en/1376/)).