> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/general/troubleshooting-cache.md).

# Troubleshooting Cache

## What is caching?

Each web page is read thousands of times more often that it is changed. Caching or using caches helps your site perform run much faster. A cache is a version of a webpage from some time in the past which assumes that the page has not been changed - and as a result does not go all the way back to our servers to check. Most caches update automatically over time - but sometimes you want to make changes get pushed out faster.   The instructions above show you how to clear each kind of cache manually to help in testing and diagnosing problems.

## How to Clear your Browser's Cache

Some browsers will hold copies of pages that have been visited before to improve performance. Select your browser for detailed instructions on how to clear cache:

* [Google Chrome](https://support.google.com/accounts/answer/32050)
* [Mozilla Firefox](https://support.mozilla.org/en-US/kb/how-clear-firefox-cache)
* [Microsoft Edge](https://support.microsoft.com/en-us/help/10607/microsoft-edge-view-delete-browser-history)
* [Safari](https://support.apple.com/guide/safari/manage-cookies-and-website-data-sfri11471/mac) (macOS) / [Safari](https://support.apple.com/en-us/HT201265) (iOS)


---

# 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://help.doctorlogic.com/docs/general/troubleshooting-cache.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.