> 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/analytics-dashboard/touchless-intelligence/touchless-document-trace.md).
# 文档追踪
在 **Document ID** 中输入文档 ID，或从集群中打开一个示例文档，即可查看**这份文档发生了什么**。
文档追踪：显示流水线路径、文档停止的阶段、该阶段掌握的信息，以及下方的运行历史。
顶部显示包含 14 个阶段的**流水线路径**：接收、分类、电子文档验证、供应商识别、文本识别、表头提取、表格提取、字段验证、采购订单查询、采购订单行匹配、审批、工作流路由、导出、ERP 确认。每个框都有一个状态：
| 状态 | 含义 |
| ------------- | ----------- |
| **已通过**（绿色） | 该阶段运行正常 |
| **在此处停止**（红色） | 该阶段阻止了文档 |
| **已跳过或不适用** | 该阶段不适用于此文档 |
| **尚未到达** | 文档尚未到达此阶段 |
| **未知**（虚线） | 此阶段没有记录任何内容 |
路径下方的句子会说明原因。截图中的内容为：*此文档在第 8 阶段“字段验证”停止，因为未提取出必填字段。* **此阶段掌握的信息**区块会列出具体信息：**无效字段数 5** 以及这些字段（`delivery_date`、`email`、`invoice_sub_type`、`payment_terms`、`supplier_id`）、规则（**REQUIRED**）和验证代码。**分析**区块会说明分析是**基于规则**还是由 AI 撰写。
下方的**运行历史**会列出每次运行（**运行 1 · 初始运行**，以及之后每次重新启动）及每个阶段记录的信息。如果文档经过更正并重新启动，备注会提醒你：该文档**仍计为已触达**。
\*\*示例。\*\*同一供应商的文档都在第 8 阶段停止。追踪中每次都会显示相同的五个无效字段。这不是单份文档的提取问题，而是字段配置中缺少默认值：修复一次，整个集群中的文档即可恢复处理。
## 相关页面
* [Touchless Intelligence](/chinese/guan-li-yu-she-zhi/analytics-dashboard/touchless-intelligence.md)
* [供应商诊断和问题集群](/chinese/guan-li-yu-she-zhi/analytics-dashboard/touchless-intelligence/touchless-supplier-diagnosis.md)
* [采购订单匹配诊断](/chinese/guan-li-yu-she-zhi/analytics-dashboard/touchless-intelligence/touchless-po-matching-diagnosis.md)
---
# 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/analytics-dashboard/touchless-intelligence/touchless-document-trace.md?ask=&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.
