workflows-history

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Zapier Workflows History

Zapier工作流运行历史

Use the public SDK CLI experimental command surface. Do not use

zapier-sdk-code-substrate

使用公开的SDK CLI实验性命令接口。请勿使用

zapier-sdk-code-substrate

。

Compatibility Gate

兼容性检查

Before using this skill, run the

workflows-doctor

bundle compatibility check. If

workflows-doctor

is not installed or cannot be loaded, run

workflows-install

or install

workflows-doctor

from

zapier/agent-skills

before continuing. If

workflows-doctor

reports SDK/skill drift, follow its refresh instructions, stop this skill invocation, reload the agent workspace if needed, and ask the user to rerun the original request.

使用此技能前，请运行

workflows-doctor

工具包兼容性检查。如果未安装

workflows-doctor

或无法加载，请先运行

workflows-install

或从

zapier/agent-skills

安装

workflows-doctor

。如果

workflows-doctor

报告SDK/技能版本不一致，请按照其刷新说明操作，停止当前技能调用，必要时重新加载Agent工作区，然后请用户重新发起原始请求。

Identify The Workflow

定位目标工作流

If the user provides a workflow ID, use it directly.

If the user refers to the workflow by name or description, list workflows first and find the matching ID:

bash

zapier-sdk --experimental list-workflows --json

If multiple workflows match, show the candidates and ask the user which one they mean.

如果用户提供了工作流ID，直接使用该ID即可。

如果用户通过名称或描述指代工作流，请先列出所有工作流并找到匹配的ID：

bash

zapier-sdk --experimental list-workflows --json

如果有多个工作流匹配，请列出候选选项并询问用户具体指的是哪一个。

Fetch Run History

获取运行历史

bash

zapier-sdk --experimental list-workflow-runs <workflow-id> --json

Parse the JSON output. Useful fields may include

id

status

started_at

finished_at

input

, and

output

When the workflow ID is known, include the Zapier editor link:

text

https://zapier.com/durables-editor/<workflow-id>

bash

zapier-sdk --experimental list-workflow-runs <workflow-id> --json

解析JSON输出。有用的字段可能包括

id

、

status

、

started_at

、

finished_at

、

input

和

output

。

当已知工作流ID时，请附上Zapier编辑器链接：

text

https://zapier.com/durables-editor/<workflow-id>

Drill Into A Run

深入查看单次运行详情

If a single deployed workflow run failed or the user wants step-level detail:

bash

zapier-sdk --experimental get-workflow-run <run-id> --json

Use

get-durable-run <run-id>

only for one-off synthetic runs created by

zapier-sdk --experimental run-durable

, not for deployed workflow runs returned by

list-workflow-runs

If a manual trigger response returns a trigger ID before a workflow run ID is available, bridge from trigger to run:

bash

zapier-sdk --experimental get-trigger-run <trigger-id> --json

Summarize the failure, status, timing, input, output, and any step error details that appear in the response. Avoid dumping raw JSON unless the user asks for it.

如果某个已部署工作流的单次运行失败，或者用户需要步骤级详细信息：

bash

zapier-sdk --experimental get-workflow-run <run-id> --json

仅对通过

zapier-sdk --experimental run-durable

创建的一次性合成运行使用

get-durable-run <run-id>

命令，请勿用于

list-workflow-runs

返回的已部署工作流运行。

如果手动触发响应返回了触发ID，但工作流运行ID尚未可用，请通过以下命令从触发信息关联到运行信息：

bash

zapier-sdk --experimental get-trigger-run <trigger-id> --json

总结响应中显示的失败原因、状态、时间信息、输入、输出以及任何步骤错误详情。除非用户要求，否则请勿直接输出原始JSON数据。

Draft State

草稿状态

Runs execute published versions — unpublished draft edits never show up in run history. If the user expects a recent change to be reflected in runs and it isn't, check for an open draft holding that change:

bash

zapier-sdk --experimental list-workflow-drafts <workflow-id> --json

If an open draft exists, tell the user their change is unpublished (note

last_edited_at

and the editor link) rather than concluding the workflow is broken.

工作流运行基于已发布版本——未发布的草稿修改不会出现在运行历史中。如果用户期望最近的修改能在运行中体现但未实现，请检查是否存在包含该修改的未提交草稿：

bash

zapier-sdk --experimental list-workflow-drafts <workflow-id> --json

如果存在未提交草稿，请告知用户其修改尚未发布（备注

last_edited_at

时间和编辑器链接），而不是判定工作流出现故障。