> For the complete documentation index, see [llms.txt](https://docs.zenlytic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenlytic.com/data-modeling/cache-refresh.md).
# Cache Refresh
Zenlytic caches your data model to keep responses fast. When you edit the model through [Context Manager](/data-modeling/context_manager.md) in the UI, the cache is invalidated automatically. When changes are pushed **directly to the underlying git repository** — bypassing the UI — the cache does not know about them.
If you or a teammate pushed changes straight to git and Zoë still appears to be using the old data model, use **Pull from Remote** to rebuild the cache from the current state of the repo.
## How to pull from remote
1. Click your workspace name in the lower left of the screen.
2. In the menu that opens, click **Account Settings**.
3. In the panel that opens, under **Preferences**, click **Pull from Remote**.
Step 1–2: open the workspace menu and select Account Settings.
Step 3: Pull from Remote lives under Preferences in Account Settings.
After the pull completes, Zoë will pick up your latest changes on the next question.
## When you need to pull from remote
* A pull request was merged directly to the production branch in git.
* A teammate pushed model changes through an IDE or command line instead of the Zenlytic UI.
* You're integrating Zenlytic with a CI pipeline that commits model files automatically.
## When you don't need to pull from remote
* You edited the model in Context Manager and used **Deploy to production**.
* You switched branches in the UI (the UI already refreshes the cache for branch switches).
---
# 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://docs.zenlytic.com/data-modeling/cache-refresh.md?ask=&goal=
```
`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.