Workflow tips — where to find the source of truth in a large graph
After PEOPLE, the showcase returns to the control/config area. For beginners, this section becomes a set of transferable rules for reading production workflows: authoritative controls, linked inputs, selectors, bypass state and checkpoints matter more than incidental widget values inside downstream nodes.
The control/config area centralizes production decisions
The source graph contains dedicated controls for generation mode, people mode, ControlNet source, working resolution, global seed, shared steps, detail strength, IPAdapter weight and other production decisions.
These values fan out downstream and control multiple branches. Reading the workflow from a control source toward its consumers is therefore more reliable than searching the canvas for duplicated settings.
A linked input overrides the local widget
If a widget displays one value but its socket receives a link from a shared control, runtime uses the linked value. A classic example is the PPL selector family: a stored widget may show 2 while linked node 543 with value 1 is the authoritative source.
CONNECTED ≠ SELECTED ≠ EXECUTED
A branch may be physically connected to a selector but not selected. A selected branch may not be required by the current output. And a required branch may return a cached result without full recomputation.
BYPASS and SELECTOR solve different problems
| Mechanism | Question |
|---|---|
| BYPASS | Should this module participate in processing? |
| SELECTOR / SWITCH | Which available data route continues downstream? |
| SHARED CONTROL | Which authoritative value drives several consumers? |
Do not fix downstream until the upstream checkpoint is proven
If the error is already present after the base decode, changing PEOPLE or upscale is wasted effort. Production debugging starts from the first incorrect checkpoint, not the final visible symptom.
Exercise: find five authoritative controls
- Generation mode 541.
- GLOBAL Seed 231.
- ControlNet source 456.
- PEOPLE mode 543.
- Working resolution 702.
- For each control, find at least one downstream consumer and verify whether its input is linked.
When the 05:42 lesson is complete
When values conflict, you look for the authoritative control and actual route first rather than trusting the nearest visible widget.