FlowBuilderSetter (adv)

FlowBuilderSetter (adv) is the advanced UI variant of the pack's FlowBuilderSetter - the flow endpoint that both runs only its upstream subgraph and stores the value flowing through it in the pack's key/value cache. The "(adv)" part swaps the plain single-run button for the advanced panel: batch looping, auto-queue, and the Disable Unrelated Nodes toggle. If you've read the 🔥FlowBuilderSetter and FlowBuilder (adv) pages, you already know both halves of this node; this variant is where the two meet.

Let's make sure the halves are clear, because they do different jobs:

• Flow half. Place it before the output you care about; its Queue button mutes everything not feeding it, runs the prompt, restores. Only the relevant subgraph executes.
• Setter half. It writes whatever flows through to CACHED_MAP[key] and passes it through its output, so a matching Getter/CachedGetter elsewhere can read it under that name. Getter key dropdowns are populated from the Setter keys in your graph.

The advanced panel then layers on batch_size looping (run the flow N times, each pass only executing the relevant subgraph), an Auto Queue toggle for continuous iteration, and the master Disable Unrelated Nodes toggle. The status readout tells you which pass you're on.

Inputs and output. Required: value (*) and key (STRING). Optional: batch_size (INT, default 1). One * output. Nothing to tune beyond the key name and batch size.

Where this actually shines. Think multi-stage video work. Stage one samples a first pass; a FlowBuilderSetter (adv) at its end gives you a button to run that stage repeatedly - generating a handful of candidate first-pass latents into the cache under pass_1 - while never touching the (expensive) stages downstream. Then you switch stages. That's the step-by-step workflow the pack's README advertises, with a repeat knob and a named handoff built in.

Gotchas to keep in mind. Execution order still rules: a Getter reading pass_1 only sees it if this node actually ran first - run the stage, then run the consumer. And the mute/restore machinery is the 2024-era JS most likely to misbehave on a current ComfyUI build (the 2025 Nodes 2.0 rewrite has already broken better-maintained packs), so test the toggles on a scratch graph before trusting a long job to it.

Install. One pack:

ComfyUI Manager → search "komojini-comfyui-nodes" → Install → restart

or cd ComfyUI/custom_nodes && git clone https://github.com/komojini/komojini-comfyui-nodes. No models. If you don't need the key/value handoff, plain FlowBuilder (adv) is simpler; if you don't need the looping, plain FlowBuilderSetter is simpler. This variant is for when you want both.