> 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/administration-and-setup/settings/global-settings/document-types/layout-manager/troubleshooting.md).

# Troubleshooting

## Troubleshooting common issues

### Fields do not match the scanned documents:

* Check the configuration of the fields in the Layout Manager and make sure they match the actual fields in the scanned documents.
* Check that the positions and dimensions of the fields in the layout are correct and that they cover all relevant information.

### Data is not extracted correctly:

* Check the validation rules and format settings for the affected fields to make sure that the expected data can be captured correctly.
* Make sure that the OCR (Optical Character Recognition) or other data capture technologies are properly configured and calibrated to ensure accurate extraction of the data.

### Faulty data validation:

* Check the validation rules for fields to make sure they are appropriate and configured correctly.
* Adjust the validation rules if necessary to ensure that they meet the requirements and formats of the captured data.

### Document layouts are confusing or inefficient:

* Revise the layout to improve the structure and organization of fields and ensure that important information is easily accessible.
* Run user testing to get feedback on the usability of the layout and make adjustments to increase efficiency.

By applying these best practices and troubleshooting as appropriate, you can create efficient and accurate document layouts that enable smooth data capture and processing.


---

# 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.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/troubleshooting.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.