Update Workflow Eval
Update a workflow eval.
Identified by eval_id. Send any of name, assertion, or source;
omitted fields are left unchanged. Returns the updated eval.
assertion: null is rejected explicitly (use Delete Workflow Eval if
you want to remove the eval entirely).
Updating source rebinds where the inputs come from:
{ type: "manual", handle_inputs: ... }— switch to hand-written inputs.{ type: "run_step", run_id: ..., step_id: ... }— re-capture inputs from a different workflow run / step.
WorkflowEval.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Body for updating a workflow eval. Only the supplied fields (name, assertion, source) are changed.
Block-eval assertion against one declared output handle.
target is the only supported shape: an output handle id and an
optional relative path inside that handle's payload.
- ManualWorkflowEvalSource
- RunStepWorkflowEvalSource
Response
Successful Response
A saved workflow eval: a target block, an input source, and the assertion evaluated against its output.
Public workflow-eval target.
The storage layer remains block-scoped today, but the API shape names the tested entity explicitly so workflow-level targets can be added later.
- ManualWorkflowEvalSource
- RunStepWorkflowEvalSource
Block-eval assertion against one declared output handle.
target is the only supported shape: an output handle id and an
optional relative path inside that handle's payload.
Single-rule schema dependency for Level 2 drift detection.
valid, drifted, broken none, partial, drifted, unknown Summary of the most recent block-eval run.
Execution status and verdict outcome are exposed as separate fields.
The summary is written on terminal-state transitions, so in practice
status is one of completed | error | cancelled and outcome is
populated when status == "completed".
Summary of the most recent block-eval run.
Execution status and verdict outcome are exposed as separate fields.
The summary is written on terminal-state transitions, so in practice
status is one of completed | error | cancelled and outcome is
populated when status == "completed".
Summary of the most recent block-eval run.
Execution status and verdict outcome are exposed as separate fields.
The summary is written on terminal-state transitions, so in practice
status is one of completed | error | cancelled and outcome is
populated when status == "completed".
When the workflow eval was created
When the workflow eval was last updated