> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-consumption/refreshing-a-report.md).

# Refreshing a report

In order to refresh your report, you can click on the refresh icon in the action bar of your report and then you are facing two options. Either refresh your report or clear all cache and then refresh your report.

<figure><img src="https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2F8Pa34c92gsqsNnpz8W7a%2Fimage.png?alt=media&amp;token=0f0c1773-3014-403f-ae17-e1da00d0bf06" alt=""><figcaption></figcaption></figure>

### Refresh

Use this option to regenerate all queries and re run them again. This is useful if your report hasn't been refreshed for a long time (more than a few minutes) and will help you refresh all your charts. You can see when your report was loaded for the last time next to the refresh icon.

### Clear cache & refresh

This is useful if you have used the refresh button but you feel like that the figures you are seeing are not up to date. When clicking on this button we will get rid of all values stored in cache and run the query against your warehouse. Be aware that this option will increase cost on your warehouse side.

If you want to be familiar with how caching works at Whaly please read:

{% content-ref url="/pages/EqaY2PRT7uppdhufRXoj" %}
[Caching](/platform-concepts/caching.md)
{% endcontent-ref %}

If you want to learn how to control cache please read:

{% content-ref url="/pages/E2p4nkOxVTurfuLq4FQF" %}
[Cache](/data-management/workbench/understanding-datasets/cache.md)
{% endcontent-ref %}


---

# 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.whaly.io/data-consumption/refreshing-a-report.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.