Stop

Explicitly terminates the current execution path. Any subsequent nodes on the same branch are not executed.

When to Use

Use Stop when you want to make it clear that execution intentionally ends here — for example, on the false branch of an If node or on the default branch of a Switch.

You do not technically need a Stop node to end a path — an unconnected output handle will stop execution silently. Stop is useful when you want:

A visible indicator on the canvas that this path ends intentionally
An optional log message recorded in the run when this path is reached

Inputs

Handle	Type	Description
`input`	any	The value flowing into this node. Not used for any logic — just signals that this path reached Stop.

Outputs

None. Stop produces no output.

Settings

Setting	Type	Description
`message`	string	Optional message logged in the job run when Stop is reached. Supports template bindings.

Example

Handle a failed payment event but ignore all other event types:

Webhook → Switch ({{ webhook.body.type }})
    → invoice.payment_failed → [retry logic]
    → default → Stop (message: "Ignored event type {{ webhook.body.type }}")

Common Gotchas

Stop only terminates the current path. Other parallel branches in the same workflow continue executing.
The log message appears in the job detail view for that specific run.