Skip to main content

​
Stop Node

Purpose: Force-terminate subflow execution immediately Stop nodes set a ForceFinish flag that exits the subflow loop, regardless of max_iterations.
Stop node visual representation
Stop node visual representation
Node Handles:
Left Side - Force Termination TriggerReceives signal to immediately terminate subflow execution.Accepts:
  • Final output data before termination
  • Completion signal from tools (e.g., “send_final_response”)
  • Error conditions requiring immediate exit
Stop nodes have no output handles. They immediately terminate the subflow and return control to the parent workflow. Use End nodes if you need to continue workflow execution.
Features:
  • Immediate Termination: Stops all remaining iterations in the subflow
  • Return to Parent: Parent workflow continues from the node after the subflow
  • Iteration Override: Bypasses max_iterations check
  • Last Output Returned: Returns the output from the most recent completed iteration
Use Cases:
  • Agent completes task and calls “send_final_response” tool → Stop
  • Error condition requires immediate exit
  • Task completion detected (no need for more iterations)
  • Resource limits reached
Behavior:
Stops the entire subflow iteration loop
Even if max_iterations = 10, the Stop Node immediately terminates the subflowParent workflow resumes immediately from the node after the subflow
Common Pattern:

​
What’s Next?

End Node

Learn the difference between End and Stop

Subflow Node

Understand subflow iteration patterns

LLM Node

Create agents that decide when to stop

Tool Node

Build “send_final_response” completion tools