> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/resources/errors-and-faqs/query-stuck-on-processing-or-chat-not-responding.md).

# Query stuck on “Processing” or chat not responding

Sometimes, after submitting a query or running a workflow, you may notice that the interface stays on “Processing…” for a long time, or that the chat stops responding altogether.

This does not always mean something is broken. In most cases, it is related to document size, session timing, or how the request was submitted.

***

#### Why this happens

This typically occurs due to one of the following reasons:

* The document or workflow is **large or computation-heavy**, which naturally takes longer to process.
* The request. or session **timed out** after a period of inactivity or brief disconnection.
* A server-level error prevented the process from completing within the prescribed time.

In these situations, the request may either still be running in the background or may have dumped the processing altogether.

{% hint style="warning" %}
A long loading state does not necessarily mean the request has failed.
{% endhint %}

***

#### What to do if processing takes too long

If a query is processing or loading for longer than expected (<mark style="color:red;">**longer than 4-5 minutes**</mark>):

* Do **not refresh immediately**, as this may interrupt the request.
* In a new tab, check the [**Matter History**](/projects/projects-homepage.md#matter-history) to see if the request has completed and the output is saved there.
* **Wait a little longer**, especially for large files or complex workflows.

If none of the above works, refresh the page and ask your query again (you may want to copy your query and paste it for the second attempt).

***

#### Best practices to avoid the issue

* For very large documents, break tasks into smaller, targeted questions.
* Avoid switching tabs or refreshing immediately after submitting a query.
* If you plan to step away, wait for the processing to begin before leaving the page.

Requests that do not fully start processing are intentionally not saved, to avoid incomplete or misleading entries appearing in [Matter History](/projects/projects-homepage.md#matter-history).

***

#### When to contact support

* If processing never completes even after waiting for over 6-7 minutes, or
* No output appears in Matter History even after processing begins


---

# 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://help.jurisphere.ai/resources/errors-and-faqs/query-stuck-on-processing-or-chat-not-responding.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.