> 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/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/layout-manager/troubleshooting.md).

# 故障排除

## 常见问题故障排除

### 字段与扫描的文档不匹配：

* 检查布局管理器中的字段配置，确保其与扫描文档中的实际字段相符。
* 检查布局中字段的位置和尺寸是否正确，以及是否覆盖所有相关信息。

### 数据提取不正确：

* 检查受影响字段的验证规则和格式设置，确保能够正确捕获预期数据。
* 确保 OCR（光学字符识别）或其他数据采集技术已正确配置并校准，以便准确提取数据。

### 数据验证错误：

* 检查字段的验证规则，确保规则适用且配置正确。
* 必要时调整验证规则，确保其符合所捕获数据的要求和格式。

### 文档布局难以理解或效率低下：

* 修改布局，优化字段的结构和组织方式，并确保重要信息易于查找。
* 开展用户测试，收集有关布局易用性的反馈，并进行调整以提高效率。

通过遵循这些最佳实践并在适当情况下进行故障排除，您可以创建高效、准确的文档布局，从而实现顺畅的数据采集和处理。


---

# 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/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/layout-manager/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.