Sequence
Runs on: Shared — pure logic, runs on the Streamerly backend or inside a chatbox overlay.
The Sequence node runs its output branches strictly one at a time, in order from top to bottom. It has a single input and several numbered outputs. The whole branch connected to the first output runs to completion — including any effects it triggers and any waits along the way — before the second output fires, and so on down the list.
Reach for Sequence when a set of actions must happen in a guaranteed order and each step is more than a single effect (a small group of nodes). Connect more branches by wiring the last output; a new one appears automatically. For ordering two individual effects, an effect's Then output wired into the next effect's Activate is usually simpler — see Ordering Multiple Actions.
Inputs
| Name | Type | Description |
|---|---|---|
input | any | The value (or pulse) that starts the sequence. It is passed through unchanged to each output in turn. |
Outputs
| Name | Type | Description |
|---|---|---|
output-0, output-1, … | same as the input | The branches, run in order. Each carries the input value. The branch off output-0 finishes completely before output-1 begins. |
Example
At the end of a giveaway you want to (1) announce the winner in chat, (2) wait five seconds, then (3) switch to your "winner" scene — always in that order. Wire your trigger into a Sequence node. Off the first output build the announcement; off the second, a Sleep followed by the scene switch. Because Sequence finishes each branch before starting the next, the announcement always posts before the scene changes, no matter how the individual actions are laid out on the canvas.
Related
- How Flows Execute — Ordering Multiple Actions — the three ways to order actions
- Sleep — pause inside a branch
- For Each — run a branch once per list item