workflow_run_stats

Tool

workflow_run_stats

Run aggregates over a time window: one row per workflow, or — with `workflow_id` — that workflow’s per-node and per-edge counts as well.

Run aggregates over a time window: one row per workflow, or — with `workflow_id` — that workflow’s per-node and per-edge counts as well. `waiting` is what is parked right now, not what was parked during the window. `done` is the synthetic end; a workflow whose node is literally named `done` is ambiguous in `edges`.

Behavior

HTTP: GET /workflow/runs/stats

Arguments

Name	Type	Required	Description
window	string	—	ISO-8601 duration back from now, `P90D` at most. Defaults to `P7D`.
workflow_id	string	—	Omitted for one row per workflow; given for that workflow’s nodes and edges too.
include_test	boolean	—	Count `workflow_run_test` runs as well. Defaults to false.

Response

Field	Type	Always	Description
runs	number	—
edges	array	—
items	array	—	One row per workflow; present only when `workflow_id` was omitted.
nodes	array	—
failed	number	—
window	string	•
waiting	number	—
last_run_at	string	—
workflow_id	string	—

Try it

Run aggregates over a time window: one row per workflow, or — with `workflow_id` — that workflow’s per-node and per-edge counts as well.

When to use

Example

Ask your agent something like this:

Run aggregates over a time window: one row per workflow, or — with `workflow_id` — that workflow’s per-node and per-edge counts as well.

The agent will invoke workflow_run_stats with these arguments:

{}