Skip to main content

Stop Node

What it does​

Stops workflow execution immediately for the current branch without sending an HTTP response.

Inputs/config​

  • Optional reason/message for audit/debug context.
  • No major runtime parameters.

Outputs/branches​

  • Terminal behavior.
  • No matched_output.
  • Does not continue to downstream nodes.

Example usage snippet​

{
  "id": "n_stop",
  "type": "stop_node",
  "config": {
    "reason": "Feature disabled for tenant"
  }
}

Common pitfalls​

  • Using stop_node in API request flows where client response is required.
  • Assuming stop triggers error branch automatically.
  • Losing observability if no reason/context is captured.