Start a flow
When a flow fails
Starts a failure handler once for each failed run of the flows it watches.
Nodes › TriggersOpen in Neblex
- Good for
- Central error handling
- Role
- Starts a flow
- Find it in
- Nodes › Triggers
When to use it
- Every failure in a project should open a ticket or reach the operations channel.
- You want one handler instead of error branches in every flow.
- The handler needs the flow's name and the error with sensitive values masked.
Reach for something else when
ErrorWhen a flow should fail on purpose when its data is wrong.AlertsWhen an email or chat alert is enough.
Example
Each failed production run opens a ticket in the service desk with the flow's name and error, and posts to the operations channel.
How it works
- Settings
- Watch every flow in this project [on], or pick the flows to watch.
- Behaviour
- Each failed production run of a watched flow in the same environment starts the handler once, with one record
{failed_run, flow, flow_name, error}; the error shows the provider's message with values masked. Cancelled runs, test runs and failed runs of handler flows never start a handler, so handlers never start one another in a circle. A handler whose start is refused (the monthly quota, storage) is tried again; Dev failures start Dev handlers only. - Example
- Open a ticket in the service desk with the flow's name and error, and post to the operations channel.
Add it to a flow
- Open the flow from Build › Workflows.
- Open Nodes and find When a flow fails under Triggers. Drag it onto the canvas as the first step.
- Connect it to the next step and open its settings with ✎ Edit.
- Save and test with Run, then set the flow Active so it starts on its own.
More in Start a flow
WebhookStarts the flow the moment another system calls its address.Nodes › TriggersForm (starts flow)Starts the flow when someone submits a form, with their answers as the input.Nodes › TriggersScheduleRuns the flow on a repeating interval or at set times.Nodes › TriggersPoll for changesChecks a system regularly and starts a run only for records that are new or changed.Nodes › TriggersLive streamSubscribes to a queue, topic or stream and runs the flow for each message as it arrives.Nodes › TriggersWhen calledMakes the flow callable by other flows, the API and AI agents, with a declared input and output.Nodes › Triggers