> For the complete documentation index, see [llms.txt](https://olab4.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olab4.gitbook.io/help/advanced-topics/cached-browser-data.md).

# Cached browser data

All interactions with OLab take place via a web browser (Chrome, Edge, Firefox etc.) In order to speed things up and make your browsing experience smoother, all web browsers now store a lot of data on your local machine so that they don't have to keep pestering the web server for the same data. This generally works smoothly and we generally remain unaware of it happening. 

But what if the data on the server changes? Sometimes your browser will keep on using the cached or locally stored version. 

The most common time that we see this with OLab is when a case author makes changes to the content: edit some nodes, changes some links… that kind of stuff. The author makes these changes in the Designer and then checks to see if these changes look ok in the Player. 

But because of the browser cache, you will see the same stuff that the server last sent you, and it looks like your changes were not saved in the Designer. 

The usual fix for this is simply to leave the map and open it again from the main list of maps. Sometimes, you may need to Logout of the Player and Login again on that same browser. You less commonly need to do this on the Designer and this is one reason why we recommend that you use a different browser for the Player and the Designer. Make sense? And when you Login back to the Player, you should now see the effects of your new edits. 

If you are having trouble with cached user credentials, try logging into a map anonymously e.g. <https://player.olab4.net/5/0> - this map requires no login credentials at all. Once you are in, you can then \[LOGOUT] again, which will clear user credentials from the browser cache.&#x20;

### Local storage

Frustratingly, this does not always work. Sometimes you also have to mess with something called Local Storage on your browser. The most common situation for this is if we have recently made some changes to OLab code and there is a new version.&#x20;

The fixes for this can become a wee bit arcane. Check out <https://olab4.net/browser-cache-problems-when-authoring/> for some other tricks to try.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://olab4.gitbook.io/help/advanced-topics/cached-browser-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.