Skip to content

Sinks & Sources

The Sinks screen lists every sink row you can see: your tenant’s sinks — machine registrations (unnamed until you name them) and the delivery definitions you create — plus the platform’s pool rows, grouped as platform. The nodes those sinks run on are managed on the Nodes screen. The Sources screen lists your trigger endpoints the same way. Both screens use the app’s standard grid: buttons on the left, Topbar search, checkboxes, and 25 rows per page. Navigate to either screen from the sidebar (Infrastructure group).


Sinks overview

A Sink is a named execution target — it exists only when it pins or constrains. The Sinks screen lists:

ColumnDescription
SinkThe row’s name (its uuid until named) and its status
PlacementThe pinned node’s name, or “any matching”
ConstraintsAttribute constraints (e.g. zone=ot) narrowing the matching pool
Used byHow many flows use this sink

Sinks table

New sink… opens the sink slide-over: name it, then pin the sink to one node or leave it as a pool — by default a sink balances across the tenant’s live sink nodes, and attribute constraints narrow the pool. A pinned sink delivers to that node alone. The flow builder’s sink picker offers the same rows — yours and the platform’s — with no other choices.

Delete with the row’s delete icon or the checkboxes + Delete Selected. When flows still use the sink, the page warns how many and offers two choices:

  • Disable — the row goes OFFLINE (out of dispatch, kept for event history); the flows stay attached and stop delivering until the sink is re-enabled or the flows are repointed.
  • Repoint & delete — every referencing flow moves to its own tenant’s platform row (or the platform default when none exists) and the row is deleted.

A sink with no attached flows deletes directly after the usual confirmation.


Sources overview

A Source is a named trigger endpoint: a platform preset plus its connection config and a placement. The Sources screen lists:

ColumnDescription
SourceThe source’s name
PresetThe platform preset it is built from
WhereThe pinned source node, or “platform”
Used byHow many flows use this source

Sources table

New source… opens the source slide-over: pick a preset from the preset catalog, fill its connection config, place it (on a specific source node, or the platform), and name it. Editing a source edits its connection config — every flow using it follows. Delete with the row’s delete icon or the checkboxes + Delete Selected.


Node health lives on the Nodes screen: each node card shows Online/Offline, its attribute sheet, and what it is currently serving. A pinned node that goes offline never falls back to the platform — its work is held (and flagged on the flow) until the node returns or a matching peer takes over.