Docs › Windmill with RunVouch
Windmill with RunVouch
Windmill has error handlers and a runs page. It does not have an outside party that notices the whole instance, or one worker group, has stopped taking jobs.
On this page
How it runs on Windmill
Inside the script (Python or Bash) with the client or rv run; Windmill scripts can shell out.
Store the key
A Windmill variable marked secret, read with wmill.get_variable("u/you/runvouch_key"), or a worker environment variable.
Wrap the job
# Python script scheduled in Windmill
import os, wmill, runvouch
os.environ["RUNVOUCH_KEY"] = wmill.get_variable("u/you/runvouch_key")
def main():
with runvouch.vouch("nightly-report", evidence=lambda: {"rows": n > 0}) as run:
n = build_report(run)
return {"rows": n}rv fails open: if RunVouch is unreachable the job still runs and you get one warning line.
Register the cadence and caps
rv agent nightly-report --cadence 24h --grace 30m --max-runtime 1h --evidence --cap-run-cost 2
Register the agent once, from anywhere with the key. Cadence is what turns a schedule that stopped into an alert; --evidence makes a run without evidence a failure; the caps pause the agent when it overspends.
What goes silent on Windmill
- A disabled schedule, or a worker group with zero workers, queues jobs without an error.
- Flow error handlers fire on failure; a flow that completes with an empty result does not fail.
What RunVouch detects
| Alert | What it means here |
|---|---|
| MISSED | cadence plus grace passed and no run started |
| FAILED | non-zero exit or a reported failure, with the stderr excerpt |
| NO_EVIDENCE | the run said ok but the file, URL or assertion you required is missing |
| STALLED | a run started and never ended within max runtime |
| RETRY_STORM | the same tool called with identical input many times in one run |
| BUDGET_RUN / BUDGET_DAY | cost cap crossed; the agent is paused until you resume it |
| DRIFT | duration or output size far off its 7-run baseline |
Need a key? Get a free key · Stuck? contact