` looks for a value at a specific path, so it can still match values the full-text index omits. Refer to [Match a JSON key](#match-a-json-key).
## Troubleshoot a query
**The search bar flags the query as invalid.** The bar validates as you type and names the problem inline, including unknown field names, unbalanced quotes or brackets, and an operator separated from its colon by a space. Fix the clause it points at.
**The query is valid but matches nothing.** Work through these in order:
1. **Check the time range.** It applies alongside the query, so a correct filter still returns nothing if the matching runs fall outside the window.
2. **Check the scope.** A clause tested against the wrong level of the hierarchy is the most common cause. Filtering traces on `run_type:llm` in the **Root run** scope matches only traces whose entry run is an LLM call, which is rarely what you want. Switch that row to **Any run**.
3. **Check for a Not applied badge.** A row on a scope the current table selection does not support is preserved but not applied.
4. **Check whether the value is indexed.** Full-text search skips URLs, stopwords, numeric-only tokens, and very short or very long tokens. Filter on a [JSON key](#match-a-json-key) instead, which is not subject to those limits.
## See also
* [View traces](/langsmith/view-traces)
* [Threads](/langsmith/threads)
* [Add metadata and tags to traces](/langsmith/add-metadata-tags)
* [Trace query syntax](/langsmith/trace-query-syntax) for the SDK and REST API query language
* [Query traces using the SDK](/langsmith/export-traces)
***
[Connect these docs](/use-these-docs) to your agent of choice via MCP for real-time answers.
[Edit this page on GitHub](https://github.com/langchain-ai/docs/edit/main/src/langsmith/filter-traces.mdx) or [file an issue](https://github.com/langchain-ai/docs/issues/new/choose).
To build a query, click the search bar and start typing:
The scopes offered, and the one selected by default, depend on the table selection:
| Table selection | Default scope | Available scopes |
| - | - | - |
| **Threads** | Any run | Thread, Root run, Any run |
| **Traces** | Root run | Root run, Any run |
| **Runs** | Single run | Single run, Root run, Any run |
If AI search is available to your organization, the scope selector also offers **AI search**, which matches results by a plain-language description rather than by query syntax. Refer to [Search with AI](#search-with-ai).
### Combine scopes
To filter on more than one scope at a time, click the 
### Scopes a table selection cannot use
Changing the table selection can leave a row on a scope the new selection does not support, such as a **Single run** row after switching from **Runs** to **Threads**. The row stays visible with a **Not applied** badge, and its query is preserved but not applied. Change the row's scope or return to a compatible table selection to apply it again.
## Query syntax
### Operators
The operators a field accepts depend on its type.
| Operator | Syntax | Matches |
| - | - | - |
| is | `field:value` | An exact match on the value. |
| is not | `-field:value` | Everything except an exact match. |
| matches | `field:~value` | A full-text search of the field. Quote the value to search for a phrase. |
| does not match | `-field:~value` | Everything the full-text search does not match. |
| wildcard | `field:value*` | A pattern, where `*` stands for any sequence of characters. |
| exists | `field:*` | Records where the field is set. |
| does not exist | `-field:*` | Records where the field is not set. |
| comparison | `field:>value` | Values above the given value. Also accepts `>=`, `<`, and `<=`. |
| inclusive range | `field:[10 TO 20]` | Values from 10 to 20, including both bounds. |
| exclusive range | `field:{10 TO 20}` | Values between 10 and 20, excluding both bounds. |
| mixed range | `field:[10 TO 20}` | Values from 10 up to but not including 20. Swap the delimiters to invert which bound is inclusive. |
Some fields accept only a subset of these operators:
* **Full-text fields**: `input`, `output`, `metadata`, and `error` accept `~` only.
* **Comparison and range operators**: These apply to numeric fields such as `latency` and `total_tokens`, to timestamp fields such as `first_token_time`, and to numeric [`metadata` paths](#match-a-json-key).
To match any of several values, combine clauses with `OR`, for example `status:error OR status:interrupted`. Listing several values inside one clause is not supported.
### Combine clauses
Combine clauses with `AND`, `OR`, `NOT`, and parentheses:
* **`AND`**: Both clauses must match. Whitespace between two clauses acts as `AND`, so `status:error run_type:llm` and `status:error AND run_type:llm` are equivalent.
* **`OR`**: Either clause must match.
* **`NOT`**: Negates the clause that follows. The `-` prefix does the same thing, so `NOT status:error` and `-status:error` are equivalent.
* **Parentheses**: Group clauses to control precedence.
`AND` binds more tightly than `OR`, so `a OR b AND c` matches `a OR (b AND c)`. Group clauses to change that: `(a OR b) AND c`.
Keywords are case-insensitive.
### Quote values
Double-quote a value that contains a space, contains a colon, or includes a character to match literally:
```text theme={"theme":{"light":"catppuccin-latte","dark":"catppuccin-mocha"}}
name:"docs agent"
tags:"env:prod"
```
Quoting also turns off wildcard matching, so `name:"docs*"` matches the literal string `docs*`. As an alternative to quoting, escape the character with a backslash, as in `name:docs\ agent`.
In the run scopes, an unquoted value containing a space splits into two clauses, so `name:docs agent` matches runs whose name is `docs` and whose indexed content contains `agent`.
### Search without naming a field
In the **Single run**, **Root run**, and **Any run** scopes, a bare term searches every [indexed field](#full-text-search-indexing):
```text theme={"theme":{"light":"catppuccin-latte","dark":"catppuccin-mocha"}}
"capital of France"
```
The **Thread** scope does not support bare-term search.
## Fields
The suggestion list groups fields into categories. The available fields depend on the [scope](#choose-what-a-filter-matches) of the filter row.
### Run fields
These fields are available in the **Single run**, **Root run**, and **Any run** scopes.
**Run attributes**
| Field | Description |
| - | - |
| `name` | Run name. Supports wildcards. |
| `status` | Run status: `pending`, `success`, `error`, or `interrupted`. |
| `run_type` | The [type of run](/langsmith/run-data-format#run-types), for example `llm`, `chain`, `tool`, or `retriever`. |
| `tags` | Run tags. A clause matches if any tag on the run matches. |
**Content**
| Field | Description |
| - | - |
| `input` | Run inputs. Use `~` to search the text, or `input.
To give the table more room, click **Hide shortcuts**, then **Show shortcuts** to bring the panel back. The **Stats** panel on the right collapses the same way, with **Hide stats** and **Show stats**.
## Save a filter
Saved views store a filter for reuse. A view belongs to the tracing project rather than to the person who created it, so anyone with access to the project can select it. In an agent-based workspace that means the view belongs to one [environment](/langsmith/agent-environments): a view saved in **Production** is not offered in **Staging**, and a filter you want in every environment has to be saved in each.
To save the current filter:
1. [Build the query](#build-a-query).
2. Click **Save View**.
3. Enter a name and description, then save.
The view then appears in the **Views** dropdown alongside **Default view**. Each entry lists the scopes its filter uses, which shows at a glance whether it applies to the current table selection.
To update a saved view, select it, change the query, then click **Save View**. To rename or delete a view, click the 
This search bar accepts the same fields and syntax as the **Single run** scope on the project page. It has no scope selector, because it always matches individual runs within the open trace. To remove the filter, click the clear icon in the filter box.
The **Visibility** options behind the