> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/cache-management.md).

# Cache Management

Open **Settings → Cache Management** to access the current cache-maintenance action.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-1b6a68772f3c6744902725fd250439234a1bd2cc%2Fsite-complete-cache-context-en.png?alt=media" alt="Current English Cache Management view with Clear Cache. No per-object TTL controls are shown; no cache was cleared."><figcaption><p>Current English Cache Management view with Clear Cache. No per-object TTL controls are shown; no cache was cleared.</p></figcaption></figure>

## Clear Cache

Use **Clear Cache** when you intend to invalidate cached data. Data may need to be loaded again afterward. Check the relevant view after the action to confirm the expected result.

The illustrated version provides this global action; it does not show a table of individual cache objects, per-object switches or editable TTL values. No cache was cleared for this illustration.


---

# 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.docbits.com/administration-and-setup/settings/cache-management.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.
