Skip to main content

Error

Use the Error step to stop a flow intentionally and record the reason. It raises a runtime error with the message you configure; the flow ends, and the message is written to the execution log.

Typical use cases include:

  • Ending a branch of a decision with a clear failure reason (for example, validation failed).
  • Surfacing upstream problems such as HTTP request failures so that the execution log shows what happened.
  • Forcing a flow to stop when downstream steps must not run.

Configure the step​

Open the flow editor, add Error, and fill in the configuration card.

Description​

  • Purpose: Make it clear what error condition this step handles.
  • When to fill it: Always. The description is shown in the editor and execution history.
  • Tips: Include the error intent, for example, Log HTTP request failure.

Error Message​

  • Purpose: The message that will be raised and recorded in the log.
  • When to fill it: Required. If no message is configured, the step falls back to No error message configured.
  • Tips: Make the message descriptive and include context from previous steps (via variables) so the log entry is actionable.

Behavior​

When this step runs:

  • The configured message is raised as an error.
  • Flow execution stops immediately; no downstream steps are executed.
  • The execution is marked as Error and the message is written to the execution log.

The Error step produces no outputs — place it at the end of a branch or wherever a flow must fail loudly.

Best practices​

  • Fail fast: Use Error immediately when a precondition is not met rather than letting downstream steps run in an invalid state.
  • Include context: Reference variables from earlier steps in the error message so the log entry tells you what went wrong.
  • Review the execution log: Logged errors can be inspected via the flow execution history to identify recurring issues.