Skip to main content

Stop with Error

Deliberately fails the run when the flow reaches it. Reach for it on a path that should never be taken—the false branch of a condition guarding an expected value—so an unexpected outcome shows up as a failed run instead of a silent success.

Fields

FieldDescription
Error MessageThe message recorded on the failed run. Accepts variables, so it can name the value that was unexpected. Left blank, a default message is recorded.

What later steps see

Nothing. The node always fails, so nothing downstream of it ever runs.

Behaviour

The failure is unhandled by design—it does not follow an error path—so reaching this node always fails the run. That is the whole point: it converts "this shouldn't happen" into something you can see in run history and alert on.

Was this page helpful?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.