> 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/more-settings/troubleshooting.md).

# 故障排除

## 即使配置得很仔细，文档处理过程中偶尔也可能遇到问题。以下是针对配置可能引发的常见问题的一些故障排除建议：

### 附加订单设置：

* 检查所有附加参数是否配置正确并符合业务要求。
* 确保配置符合系统要求和用户需求。

### 导出到 IDM：

* 确保与 IDM 系统的连接配置正确，并已具备所有必要权限。
* 检查文档格式是否符合 IDM 系统的要求。

### 附加容差设置：

* 确保容差限值切合实际且可行。
* 定期检查容差限值是否符合当前业务要求。

### 备用文档导出：

* 使用不同格式测试导出，确保所有所需信息都已正确导出。
* 确保导出格式符合接收方或目标系统的要求。

### 订单停用状态：

* 检查状态停用配置，确保其不会造成不必要的工作流阻塞。
* 确保所有用户都了解状态变更，并知道如何应对。

应用这些设置和最佳实践后，组织可以简化文档处理流程、提高数据准确性并确保符合法规要求。


---

# 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/more-settings/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.