Run independent actions in parallel
When two actions do not depend on each other, run them at the same time instead of back to back.Flows run top to bottom by default. If one action waits on a slow reply from Twitch or OBS, everything after it waits too, even when the next step has nothing to do with the first.
The recipe
- Drop a Parallel node where the work splits.
- Wire each independent action onto its own branch: post to chat, switch an OBS scene, update a Stream Deck button.
- The flow continues once every branch has finished.
When you are repeating the same work across a list (a raid's team members, a set of scenes), reach for For Each Parallel so each item runs on its own branch instead of in sequence.
Only split steps that share no data. Parallelizing a step that needs the previous step's result just reintroduces the wait you were trying to remove.