> 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/dynamic-components/component-builder/interactions/refresh-query.md).

# Refresh Query

The Refresh Query interaction reloads a specific component's query and updates the data it displays.

## Overview

The Refresh Query interaction refreshes a component's query and updates the data it displays. Unlike [**Refresh All Queries**](/dynamic-components/component-builder/interactions/refresh-all-queries.md), which refreshes broadly (the whole page or the whole current component), Refresh Query targets specific components by API name — giving you precise control over what gets re-fetched.

Use it when a data change only affects one or two components and you want to avoid re-querying everything else on the page.

***

## Configuration

* Add the interaction where you need it (e.g., in the On Success chain of a record operation).
* Action Type: Select `Refresh Query`.
* **Components to refresh**: The API names of the components whose queries should be refreshed.
  * If you leave the list empty, the current component is refreshed.
  * To refresh the triggering component alongside others, include the Current Component option in the list.

***

## Example

Goal: A form updates a Contact, and only the "Related Contacts" Data Table should reload.

1. Update Record: Saves the Contact changes.
2. On Success -> Refresh Query: Add the Data Table's API name (e.g., `RelatedContactsTable`) to the Components list.
3. On Success -> Show Toast: Confirms the save.

Result: Only the targeted Data Table re-runs its query — the rest of the page is untouched.


---

# 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/dynamic-components/component-builder/interactions/refresh-query.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.