Workflows

The Workflows block runs long-lived business processes: multi-step sequences that pause for human approval, wait on external events, and resume hours or weeks later without holding a connection open.

The property that matters

A workflow is durable and suspendable. It can stop mid-process, survive a restart of every service involved, and continue where it left off when a signal arrives. That is the whole reason this block exists separately from Jobs — a job runs to completion; a workflow waits.

Anything with an approval step is a workflow. Expense sign-off, onboarding with a manager gate, a refund needing review — all of them spend most of their wall-clock time doing nothing, and none of them can be modelled as a long-running function call.

Next

• Usage — the API and how to drive it
• Operations — configuration, running it, and what to watch