Shapes

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

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.

  1. When a flow fails
  2. Build text
  3. Jira
  4. Slack

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.
More in the guide

Add it to a flow

  1. Open the flow from Build › Workflows.
  2. Open Nodes and find When a flow fails under Triggers. Drag it onto the canvas as the first step.
  3. Connect it to the next step and open its settings with ✎ Edit.
  4. Save and test with Run, then set the flow Active so it starts on its own.