Automation Runs, Waits, and Approvals in Velveteen
Updated August 16, 2026
Runs are durable records. They can wait for a date or event, pause for an approval, and resume from the same node without duplicating effects.
The run timeline shows the current state, lease, redacted step output, approval snapshot, and next safe action.
States to know
Waiting
A durable time or domain-event wait owns the next wake-up.
Approval required
An authorized person must approve the exact effect snapshot.
Blocked
A policy, ownership, scope, or dependency issue needs attention.
Unknown outcome
The provider result is reconciled by effect key before any retry.
Frequently asked questions
Can I approve a changed step?+
No. A changed graph or effect fingerprint invalidates the old approval.
Related articles
Automations overview
A central workflow hub for release operations, recipes, custom automations, runs, waits, approvals, and recovery.
Runs and recovery
Read a run timeline, approve high-impact steps, reconcile unknown outcomes, and recover without duplicating effects.
Activating and managing
Review a draft, activate an immutable version, and pause or delete it safely.