[Legacy] Multi-route

Multi-route is the predecessor of the Flow Orchestrator's per-stage option list: one node, up to three alternative processing chains, and a selector for which one runs this time. It's [Legacy], hidden from the add-node menu, and only shows up when you load an old workflow that used it. It works fine if you've got one of those; for new work, the Flow Orchestrator is the same idea done properly, with unlimited options and stage-order protection you don't get here.

How it works

You give the node an input channel (the previous stage's result, default 上一阶段/"previous stage") and an output channel (where the result gets published, default 本阶段/"this stage"). The route dropdown has four choices: 旁路 (bypass) plus 方案 1 / 2 / 3 (option 1/2/3), each backed by an optional input socket (option_1, option_2, option_3).

The execution logic is one sentence: run the selected option and nothing else. The node is lazy, so check_lazy_status only requests the socket for the route you picked - the other two branches aren't computed, which is the whole point versus running everything and throwing most of it away. If you select bypass, or the selected option isn't connected, it falls back to the source input and passes the previous stage through. No valid option and no source means a blocked error instead of silent garbage.

What you set

• input_channel / output_channel - names for the pass-through and the published result.
• route - the dropdown: bypass or one of three options.
• option_1 / option_2 / option_3 (any) - wire each branch's output here. Each one is a candidate result chain.

The single output, 选择结果 ("selection result"), is whichever branch won. The UI text here is the older Chinese-facing set - this pack ships both English and Simplified Chinese, and the legacy nodes kept their original labels.

Why it's legacy

Three hard-coded options is the tell. The orchestrator that replaced it does unlimited alternatives per stage, auto-selects the first available non-bypassed option, and validates that each option actually reads the correct previous stage's result. Multi-route has none of that - you pick, it runs, and a wrong read silently passes through. Keep it in old workflows; build new ones with the orchestrator.

Install

The pack installs like any other: flow-branch from ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/yurishk/ComfyUl-FlowBranch

then restart. No Python dependencies, no models. And a small navigational note: since it's hidden from the node picker, don't go hunting for it when adding nodes - it appears only when an old workflow references it.