A run that fails on purpose, on somebody's phone
The same pipeline told twice: a push node says "this finished" when it does, and a run-outcome hook says "this failed" when it doesn't. Run it with no input and the validate node fails the run, so the failure hook raises the alert; run it with { "rows": 5 } and the node at the end raises a different one. Both land in the alert inbox and on every paired device — and they are recorded even when nothing is paired, so an alert is never lost for want of an audience. This demo needs no docker stack: the audience is a phone, not a database.
The pipeline
This is the actual graph the template creates — 2 steps.
Connects to
- Nothing outside SpanFlow
How you know it worked
Run the pipeline with no input. It fails at "Did anything arrive?" (nothing supplied a row count), and one alert appears: severity error, "Nightly load failed", raised by the run-outcome hook — its source reads 'hook', not a node.
Try this templateUsed in: Healthcare & laboratories
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.