Skip to main content

What is error branching?

Error branching in a workflow allows for graceful execution when a destination node fails. In the event of a failed node, downstream nodes on the happy path will not execute, but an error branch allows for error handling. Error branches should be used along with event monitoring to ensure proper processing.

When do I use error branching?

Receive a custom Slack message when a credit card errors in a form.

How do I add error branching?

  1. Select the node where error branching should happen. Go to Advanced Settings and turn Continue when this action fails on.
  2. Build the success branch
    • Add a filter below the destination action: !parentActionErrored()
    • Build out the happy path below the filter.
  3. Build the error branch
    • Add a branch to a filter below the destination action: parentActionErrored()
    • Build out what should happen when the action fails.

Accessing the error message

The specific error message returned by a failed node may require some CEL to access. Formatting of the error message is highly dependent on where the error is coming from. Each error message contains an issue and details:
  • issue — what you see on the issue monitoring page (e.g. Third party API call failed)
  • details — the full error message body. Formatting varies depending on the source of the error.
Error message:
Slack message CEL: