Skip to main content

Start node

Control

The Start node is the explicit entry point of a workflow. Every canvas has exactly one. It marks where the runtime begins the graph walk when a run is dispatched. Start has no configurable options — it's a pure structural marker.

When to use

  • Always. Every workflow has exactly one Start node; the canvas creates it automatically for a new project.
  • Multiple Sources on one canvas all attach their in port to Start (Start -> Source A, Start -> Source B); the runtime dispatches them in parallel when their downstream branches are disjoint, or serially when they share a downstream node.

Ports

PortDirectionKindCardinalityNotes
outoutdatamanyFires once at run start. Every reachable Source picks up its in edge from Start.

Configuration

None. Start has no config surface.

Runtime behaviour

  • At run start the runtime finds Start, marks it SUCCESS immediately, and walks the outgoing edges to enqueue the reachable Sources.
  • Multi-source dispatch: when Start has multiple out edges and each edge leads to a Source, the runtime decides parallel vs serial based on downstream topology (parallel if the branches are disjoint; serial if they share a downstream node).