> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/validation-screen/troubleshooting.md).

# Troubleshooting

If a value is missing on the validation screen, first check whether the text is visible in the document and whether DocBits recognised it. This helps you tell a reading problem from a field or rule problem.

1. Open the affected document in **Validation**.
2. Compare the original document with **OCR view**. Check the same page and the same area where the value should appear.
3. If the text is missing from OCR view, follow [Missing Text in OCR Extraction](/end-user-and-partner-section/end-user-section/validation-screen/troubleshooting/missing-text-in-ocr-extraction.md).
4. If the text is present in OCR view but the field stays empty, ask an administrator to check the document type's field setup. Include the document type, field name, page and a safe test example.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-f8fee4b8b14a79fb2ae80bdd25cb3c32bda04937%2Fdbdc238-validation-ocr-en.png?alt=media" alt="English OCR view of a synthetic invoice in Validation"><figcaption><p>Current English Sandbox OCR view of a synthetic Test A invoice. The sample is for orientation; it does not show a failed extraction.</p></figcaption></figure>

Do not include customer documents or personal data in a support screenshot. The [Validation Screen overview](/end-user-and-partner-section/end-user-section/validation-screen.md) explains the main controls if you are new to this screen.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/end-user-and-partner-section/end-user-section/validation-screen/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.