Nodes/WAS_Extras/Wan 2.2 MoE Conditioning Append (WAS)
ComfyUI Node

Wan 2.2 MoE Conditioning Append (WAS)

Chaining conditioning lists for Wan 2.2's MoE sampler

By WASasquatch·Created 3 years ago·Updated 17 days ago· 43
Wan 2.2 MoE Conditioning Append (WAS)
  • cond_a
  • cond_b
  • conditioning
  • count

Wan 2.2's biggest architectural change from 2.1 is the split into a high-noise and a low-noise Mixture-of-Experts model (27B total, 14B active at once), each handling a different part of the denoising trajectory. Once you're building workflows that want more control over that than a single straight KSampler pass gives you, you need a way to hand multiple conditionings to a multi-stage sampler in a defined order. That's what Wan 2.2 MoE Conditioning Append (WAS) is for - plumbing, not magic.

How it works

This is a list builder, not a blender, and that distinction matters. It takes cond_a and cond_b - each of which can itself already be a list of conditionings, per the node's own tooltips - and appends them into a single combined CONDITIONING output, plus a count telling you how many entries are now in it. That's different from stock ComfyUI's Conditioning (Combine), which merges tensors together into one; this one keeps entries as discrete items in a list, closer to Python's list.append. Chain a few of these together (feed one's conditioning output into the next one's cond_a) to build up a longer sequence, and use count as a quick sanity check that you actually queued as many entries as you meant to before it reaches WAS's companion Wan 2.2 MoE Sampler node, which is what actually consumes the list.

The inputs and outputs that matter

  • cond_a (CONDITIONING, required) - "first conditioning or list of conditionings," per its tooltip.
  • cond_b (CONDITIONING, required) - same, second slot.

Outputs: conditioning (the combined list - this is what you wire forward, either into another Append node or into the MoE sampler) and count (INT, how many entries the list now holds - useful to route into a preview/debug node while you're setting a chain up).

How to install it

Via ComfyUI Manager: search WAS_Extras, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/WAS_Extras

Restart ComfyUI. No model files, no extra dependencies - this is pure Python list plumbing.

Common issues & troubleshooting

Your extra conditioning seems to get averaged away instead of staying distinct. You're probably feeding this node's output into a plain KSampler, which doesn't understand a conditioning list the way the pack's own MoE Sampler does. This node's output is built for that companion consumer specifically - check you've got the right sampler downstream.

count isn't going up the way you expect. Usually means you fed already-merged conditioning (say, something that already went through a stock Conditioning Combine) into cond_a/cond_b, so what looks like one entry to this node actually collapsed several upstream. Chain raw or list conditioning through directly instead.

Can't find much community chatter about this exact node when something looks wrong. Fair - it's one of the newer, Wan-2.2-specific additions to a small pack, not a headline node. For what it's worth, WAS_Extras isn't a ghost repo: its sibling ConditioningBlend node (a different node in the same pack, for blending two conditionings rather than listing them) gets recommended on r/comfyui as an alternative to stock Conditioning Combine - real evidence people are actually running this pack's conditioning tools, even if this specific node hasn't generated its own threads yet. If you hit a genuine bug, the pack's GitHub issues are a better bet than searching Reddit.

Categoryconditioning

Inputs (2)

NameTypeDefaultDescription
cond_aCONDITIONINGFirst conditioning or list of conditionings.
cond_bCONDITIONINGSecond conditioning or list of conditionings.

Outputs (2)

NameTypeDescription
conditioningCONDITIONING
countINT