> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/troubleshooting/how-to-force-update-your-app.md).

# Force Update Your App

Most modern browsers will cache applications. When Limio makes a new release or a hotfix, it can happen that the browser caches an older version of Limio for a few days. Here are a couple of ways to force a refresh:

{% embed url="<https://www.loom.com/share/da57b30388934f0990461a6e084e7206>" %}

*Note: This only updates the browser it was performed on. So after an environment upgrade, this will need to be performed by **each individual user** that enters the app.*

**Hard refresh step by step:**

* *Windows users:* hold down Ctrl and then press F5 on your keyboard
* *Mac users:* hold down CMD and Shift and then press R on your keyboard

**Clear cache steps by step:**

* Right click > Inspect
* Click on Network > Check the Disable Cache checkbox
* Click on Application > Clear site data button


---

# 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.limio.com/support/troubleshooting/how-to-force-update-your-app.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.
