> 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/workflow/workflow-logs.md).
# 工作流日志
## **概述**
**工作流日志**允许用户分析某个文档执行了哪些工作流、了解执行结果，并深入查看条件级别的详细信息，以便进行调试或验证。
## **访问工作流日志**
要访问工作流日志：
1. 前往**仪表板**。
2. 点击所需文档旁的**操作菜单**（三点图标）。
3. 从菜单中选择**工作流日志**。
* **注意**：必须启用工作流功能才能访问此选项。
4. 将打开一个**侧边面板**，显示已执行工作流的摘要。\\
## **工作流日志面板的组成部分**
#### **1. 工作流摘要计数器**
位于日志面板顶部：
* **蓝色**：已执行工作流的总数。
* **红色**：以**错误**结束的工作流。
* **黄色**：因条件不匹配而**未完成**的工作流。
* **绿色**：已成功**执行**的工作流。
#### **2. 工作流执行表**
表格中的每一行代表一次工作流执行，包含：
* **工作流名称**
* **时间戳**（创建时间）
* **运行时间**（秒）
* **结果图标**：
* 绿色勾号：工作流已成功执行。
* 红色叉号：工作流执行时发生错误。
* 橙色短横线：由于未满足条件，执行已停止
点击每行左侧的**箭头**可展开**工作流详细信息视图**。
### **工作流详细信息视图**
点击某个工作流行会打开其**详细执行日志**，其中显示：
#### **条件评估**
* **When...** 区块：初始条件。
* **And...** 区块：附加条件。
* **Then...** 区块：所有条件均满足时执行的操作。
每个条件行会显示：
* **绿色勾号**：条件已满足。
* **橙色短横线**：条件未满足。
* **红色叉号**：条件因**错误而失败**
### **重要行为说明**
如果工作流中的某个条件**未满足**，系统会**停止评估该工作流中的所有后续工作流卡片**。此行为可避免不必要的处理\
作为视觉提示，**未满足其条件**的卡片会显示为**灰色**，同一工作流中的所有**后续卡片**也会显示为**灰色**，表示它们**尚未执行**。
---
# 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/workflow/workflow-logs.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.
.png?alt=media)
