> 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/parallel-review-tool-job-failed.md).

# Parallel Review tool: Job Failed

{% hint style="warning" %}
The Parallel Review tool is designed for **batch analysis of uniform documents** (e.g., multiple agreements or invoices). It may fail if documents are scanned without OCR, if extraction queries are too broad, or if mixed/uneven file types are uploaded.
{% endhint %}

Sometimes when you start a **Parallel Review tool** task, you may see a failure notification (a red ❗ icon or error message) indicating that the **Parallel Review tool job failed** for the selected documents.

> Example message:\
> `Parallel Review tool job failed for: [filename].pdf/.docx`

***

### Possible Causes

1. **OCR failed**
   * If you upload scanned PDFs that don’t have a text layer, and OCR processing fails, the Parallel Review tool cannot read the contents to generate a table. [Make sure your documents are OCR'ed - or do it on Jurisphere itself](/file-upload-and-management/your-files-and-documents.md#when-is-manual-ocr-needed).
2. **Overly complex extraction query**
   * The Parallel Review tool is designed for **structured extraction, i.e.,** building tables across many similar documents.
   * If your instructions require a very complicated task (e.g., *“Draft a notice based on each document”*), the job may fail because it is outside [the Parallel Review tool’s scope](/parallel-review/overview-of-the-parallel-review-tool.md).
3. **Non-uniform or mixed document types**
   * The Parallel Review tool works best when you upload **multiple, similar documents** of the same type — for example, 100 agreements, or 100 invoices.
   * If the selected files are very different (e.g., a mix of contracts, bills, and letters), or if the formatting is inconsistent, the system may not be able to align them into a coherent table.
4. **Corrupted or protected files**
   * If a file is password-protected, corrupted, or unreadable, processing will fail.
5. **Backend / processing hiccups**
   * Temporary system errors in the queue may occasionally interrupt processing.

***

### Troubleshooting Steps

1. **Check OCR**
   * If your PDFs are scanned, run OCR before uploading.
   * Confirm you can select and copy text from the PDF.
2. **Simplify your** [**extraction query**](/parallel-review/using-the-parallel-review-tool.md#formulating-queries)
   * Frame instructions as **clear, column-based extractions**.
   * Example:
     * ✅ “Extract clause number, party names, and effective date into a table.”
     * ❌ “Draft a legal notice based on each document.”
3. **Upload uniform document sets**
   * Use the Parallel Review tool for **sets of similar documents** (e.g., all invoices, or all lease agreements).
   * Avoid mixing unrelated document types in a single run.
4. **Verify document integrity**
   * Re-save documents in `.docx` or text-searchable PDF format.
   * Remove password protection if applied.
5. **Retry the job**
   * After applying the above checks, re-run the extraction.
6. **Contact support**
   * If the error persists, reach out via the in-app support channel with:
     * The type of documents uploaded (e.g., invoices, agreements)
     * The extraction query you used
     * A sample of the failed files (if possible)


---

# 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/parallel-review-tool-job-failed.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.