Workflow concepts
Use this glossary while reading a run. For the full lifecycle, see How Workflows Run.
Definitions and versions
A definition is a saved recipe: its inputs, outputs, steps, and dependencies. A run keeps its selected workflow and child versions even after later edits or imports. Eligible Command retries have a limited exception.
Runs
A run is one execution, with its inputs, progress, results, and evidence recorded locally. Its optional task or project association supplies defaults; explicit step targets can select other work.
| Status | Meaning |
|---|---|
pending | Ready to begin |
running | Work is progressing |
waiting | Paused for work, evidence, or a decision |
blocked | Needs intervention or an applicable recovery action |
failed | Ended unsuccessfully |
completed | Finished successfully |
cancelled | Orchestration stopped |
Steps and attempts
A step is one unit of work. An attempt is one execution of that step. Retrying adds an attempt and preserves the earlier record.
Inputs and outputs
Inputs supply values a run needs. Steps declare named outputs for later steps; the workflow publishes only its declared final results. Evidence is the supporting record, such as a session outcome or review verdict.
Use needs whenever a step depends on another step or consumes its output. Visual placement does not establish execution order. See expressions and outputs.
Waiting states and human gates
An Await Condition waits for an authored agent, review, or callback outcome. A Human Gate waits for an authorized operator’s approval decision or answers to authored questions in Valdr UI.
Child workflows
A parent runs an exact saved child version, supplies its declared inputs, waits for completion, and maps selected child results into its own outputs. Both runs remain inspectable.
Review and approval outcomes
| Decision | Values |
|---|---|
| Verified review | review_approved, review_changes_requested |
| Human gate | approved, rejected, answered |
approved and rejected are decision outcomes; answered records responses to a Questions gate. An answer submission is not an approval. Review evidence cannot replace a human decision, and human approval cannot replace independent review.
Recovery
Retry step repeats an eligible attempt; Run again creates separate history using the same workflow versions. You can edit declared inputs, including task and project targets; the original run association and context stay fixed.
Cancel run stops orchestration; see cancellation scope. Delete run permanently removes history and, by default, linked sessions. Read the recovery controls and deletion consequences before acting.
Next step
Run Your First Workflow takes one prepared task through implementation and review.