> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/budgets-and-forecasts/contributor/refresh-a-workbook.md). # Refresh a workbook Clear the cache and ensure you have the most up-to-date data. {% hint style="info" %} User permission: Budgets & Forecasts {% endhint %} Refreshing a budget or forecast workbook is useful when you have already tried a browser refresh, but still do not see the expected results - the issue is usually because the cache has not been refreshed. You might need to refresh the workbook if there is a change in the underlying database, such as a change in user permissions. It is also required when you are using one database as a driver in another. For example, if you have a Sales budget published to a stream that is used to create a Financial budget, when you edit the sales values and republish the budget, the values might not automatically update in the Financial budget. If you refresh the page and the updates still do not flow through, you can use the **Refresh workbook** option to clear the cache data and reload the page. Click the **Budget** (or **Forecast**) menu and select **Refresh workbook**. --- # 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.phocassoftware.com/budgets-and-forecasts/contributor/refresh-a-workbook.md?ask=&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.