> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/resolving-caching-issues-in-reo.dev.md).

# Resolving Caching Issues in Reo.Dev

If you're experiencing issues with the Reo.Dev web application due to caching, follow the steps below to clear cached data and restore functionality. This guide provides a step-by-step method using Developer Tools in your browser.

***

### **Steps to Resolve Caching Issues**

#### **1. Access Reo.Dev Web Application**

* Open your browser and go to: <https://web.reo.dev/login>.

![](https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FyMKqUe0Kpjll2JXZAash%2FScreenshot%202026-03-18%20at%2011.54.18%20AM.png?alt=media\&token=dcd1ab35-c202-4e7c-8d46-ff18f22c8beb)

#### **2. Open Developer Tools**

* Right-click anywhere on the page and select **Inspect**.
* This will open the **Developer Tools Panel**.

#### **3. Clear Local Storage**

* In the Developer Tools Panel, go to the **Application** tab.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e5359522-8649-4211-93c9-af1cf52a0355/2a212454-a0fa-4d92-9f8e-5f94aadcee30/images/c723d84f-4d1a-4c52-b0ba-9ac647e02473.png)

* In the left panel, expand **Local Storage** by clicking the arrow icon.
* Right-click on `https://web.reo.dev` and select **Clear**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e5359522-8649-4211-93c9-af1cf52a0355/2a212454-a0fa-4d92-9f8e-5f94aadcee30/images/95157686-6d95-4a30-a279-5977401008d4.png)

#### **4. Clear Session Storage**

* In the left panel, expand **Session Storage**.
* Right-click on `https://web.reo.dev` and select **Clear**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e5359522-8649-4211-93c9-af1cf52a0355/2a212454-a0fa-4d92-9f8e-5f94aadcee30/images/e8892412-25cb-4865-9461-ec9af0e2ec44.png)

#### **5. Refresh the Browser**

* Close the Developer Tools Panel.
* Refresh the page.
* The **Submit** button should now be active.

***

### **Troubleshooting**

| Issue                           | Solution                                                                 |
| ------------------------------- | ------------------------------------------------------------------------ |
| Submit button is still inactive | Ensure all storage (Local & Session) has been cleared and refresh again. |
| Page still not updating         | Try opening the site in an incognito/private window.                     |
| Persistent caching issues       | Clear browser cookies and cache or try a different browser.              |

***

### **Additional Notes**

* These steps are applicable to **Google Chrome, Edge, and other Chromium-based browsers**.
* If using **Firefox**, follow similar steps under **Storage Inspector** in Developer Tools.

If you need assistance with the implementation, contact your **Customer Success Manager** via the Slack channel or email us at [**support@reo.dev**](mailto:support@reo.dev)


---

# 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.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/resolving-caching-issues-in-reo.dev.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.