Runs
Watch it run. On the graph you built.
Nodes light up as the run goes: pending, running, done, failed. No kubectl. No separate log tool.
The problem
You can't see the run without kubectl.
Checking on a workflow means kubectl, or a tab nobody has open. The person doing the nightly export by hand keeps doing it by hand.
While it runs
Live status, node by node.
Status from the cluster lands on the node it belongs to, while the run is still going.
- A failed step centers the canvas and shows its error. Click back to it any time.
- Rerun a finished run in one click, same parameters.
- Email or Slack the moment a run fails, or a connector goes offline.
the rail, mid-run text
live run RUNNING 3/5 nodes elapsed 02:14 ETA ~00:40
fired by github
✗ test exit code 1: assertion failed on row 41 Triggers
Every trigger lands on the same canvas.
A run started by a webhook overnight shows up exactly like one you clicked.
triggers text
manual -> run it now, from the canvas
cron -> scheduled here, or a real CronWorkflow
webhook -> shared secret, or HMAC + nonce
github -> push / pull_request / tag
sns -> a topic, signature verifiedWatch your next run on the canvas.
dagweave is in early access. Leave an email and we will bring you on as we open it up.