> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/faq-and-troubleshooting/data-is-not-loading.md).
# Data is not loading
If your data is not loading, there might be many potential causes for this. This might as well render differently in the UI component: the infinite load, or the error.
In this article, we'll review the most common causes of this issue and help you identify and fix the problem.
#### Case 1 - VPN
A user supposedly hasn't changed anything but started to get this error:
**Solution:** Disabling VPN solved the problem - this is the most common reason for such an error. After disabling it, reload the page.
Case 2 - SQL query filters
In this case, a user wanted to display a filtered collection from a custom SQL query but got the "Nothing found" message
Even though the query was correct, it didn't account for the fact that Jet handles filtering automatically, so you **should not** add the `WHERE` clause.
**Solution:** omit `WHERE` and only set up the inputs and reference them in the query.
---
# 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.jetadmin.io/faq-and-troubleshooting/data-is-not-loading.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.