Skip to main content
triage-run is an archived example and is not installed by init. Copy it from examples/init-pack/ with its dependency closure, or ask create-workflow to build an equivalent. Once installed, run it with the command below. triage-run takes a single run id, pulls that run’s state and recent event log, diagnoses the most likely root cause, and recommends the exact next move: fix, rewind, retry, or escalate. Reach for it when a run failed or stalled and you want a grounded read plus a concrete command instead of eyeballing the logs.
The input is targetRunId, not runId: the engine reserves input.runId for a run’s own id, so a workflow that inspects another run needs a distinct name.

​
Stages

  1. gather: deterministic (no agent): shells inspect <targetRunId> --format json and events <targetRunId>, returning the run state, its run-level runError, its failingNodes, any pendingApprovals the run is suspended on, the tail of lastEvents, an ok flag (false when inspect could not be read), and a one-line summary.
  2. diagnose: an agent reads the gathered evidence and names the single most likely rootCauseHypothesis, with supporting evidence and a confidence level. Pending approvals are read as a stuck state, not a failure; recurring identical errors point at a persistent defect, one-off network resets at a transient one.
  3. recommend: an agent proposes one recommendedAction (fix | rewind | retry | escalate), the exact command to run next, and a rationale. A run waiting on an approval is always escalated, never rewound or retried.
It does not mutate the run. Every stage is read-only, so the recommended command is yours to run.

​
Inputs

​
Monitor it