End Node
The End node marks where a workflow graph finishes. Reaching an End node signals the orchestrator that the happy path is done.
End is inserted automatically when you create a new workflow and does not appear in the node palette.
When to use
Section titled “When to use”Every top-level graph needs at least one End node. Graphs can have multiple End nodes (e.g. one for the success path and one reached via a conditional “error” branch) — each End just records completion for the scope it runs in.
End is not used inside fan-out templates; templates use Out markers instead.
Configuration
Section titled “Configuration”None. The property panel shows only the common header fields.
Behavior
Section titled “Behavior”- When cascade reaches End, it is inserted as
completed, mirroring its input intooutput_data. - Cascade is invoked once more from End, but End has no outgoing edges, so this is a no-op — the call is kept for idempotent logging.
End never runs on a minion and has no billable compute time.
Validation rules
Section titled “Validation rules”- End must not have outgoing edges.
- End must not appear inside a fan-out template.