> For the complete documentation index, see [llms.txt](https://overleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://overleaf-pro.ayaka.space/latex/knowledge-base/163-why-does-it-sometimes-take-a-lot-of-time-to-show-the-pdf-preview.md).

# Why does it sometimes take a lot of time to show the pdf preview?

This may be due to errors in the document that you're working on—the preview will only update when the document can successfully compile. Any errors thus prevent the preview from updating, and it will remain displaying the last successful compile until the errors are corrected.

You can see any errors in your document by moving your mouse over the word 'error' in the top right of the preview. For example, a common error is the need to put mathematical symbols in dollar signs, e.g. $$\phi$$ instead of just \phi.

If the PDF preview does not update even when the errors are resolved, please [let us know](https://www.overleaf.com/contact) and we'll take a look for you.


---

# 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://overleaf-pro.ayaka.space/latex/knowledge-base/163-why-does-it-sometimes-take-a-lot-of-time-to-show-the-pdf-preview.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.