What it is
A workflow is ours: written as a page in docs/workflowdb, shipped inside this
image, and run here. Windmill, the edge functions and firecracker are the
runtimes a step calls, not the place a workflow lives, so one run can fetch with
a Windmill script, compute in a microVM and hand off to an edge function, each
step reading the output of the ones before it through ${steps.<id>.output}.
Steps run in order unless after says otherwise, and independent steps run
side by side. Each has a timeout, retries with backoff and an optional when.
A failed step blocks only what depends on it. Runs and every step’s input and
output are kept in the workflows schema for 30 days, and a run in flight when
the pod restarts picks up where it stopped.
/api/workflows reads for DASHBOARD_VIEW and starts or cancels for
DASHBOARD_MANAGE. A workflow can also start on a five-field cron (UTC) or from
a webhook signed with x-kbve-signature: sha256=<hmac>.
Workflows is where they are run and watched.
Discuss on the forum
Questions, fixes and notes on this page live in the KBVE forum.