For the built-in ControlNet Apply node, the documentation lists positive and negative as conditioning inputs and outputs, and says either output can go to another ControlNet or a K Sampler. For ControlNetApplySD3 specifically, its documentation says that when reused conditioning already contains control information, a new ControlNet is linked after the previous one; that node is marked deprecated and may be removed in future versions. The A-to-B handoff below is an audit pattern for that documented SD3 behavior, not a universal rule for every Apply node, version, or custom node. Check the documentation for the node you use. A wiring audit confirms connections, not that the generated image will look right.
Map the two branches before connecting
In the built-in ControlNet Apply documentation, positive and negative are both CONDITIONING inputs and both are returned as outputs. The outputs can go to another ControlNet or to a K Sampler. Use that interface as the audit rule: at every stage, record where each input comes from and where each output goes.
Name the starting pair Base positive and Base negative. After the first node, call its outputs A positive and A negative; after the next, B positive and B negative. These labels describe connection provenance, not separate ComfyUI features.
Connect the chain in order
- Connect the positive and negative text-conditioning sources to the matching inputs of ControlNet A. Connect A’s own control model, preprocessed image, and the other required inputs separately.
- For the documented
ControlNetApplySD3sequential behavior, connect A’spositiveoutput to B’spositiveinput, and A’snegativeoutput to B’snegativeinput. This traces the reused conditioning that already contains A’s control information. Do not treat this as a verified requirement for other node implementations; check their documentation. If B is intended to follow A, routing B from the original text-conditioning sources instead bypasses A’s outputs in the graph. - For a further
ControlNetApplySD3in the documented sequential workflow, continue tracing the reused positive and negative outputs into the next node’s matching inputs. For other nodes, verify their documented behavior before assuming sequential linking. - Connect the last node’s positive and negative outputs to the sampler’s matching conditioning inputs. For a one-ControlNet workflow, use that node’s outputs directly at the sampler.
- Trace each wire visually from source to destination and write its source in the worksheet below. Check for crossed positive/negative wires as well as accidental bypasses.
The SD3 Apply documentation explicitly describes linking a new ControlNet after a previous one when reused conditioning already contains control information, and lists both conditioning outputs. This is node-specific documentation: ControlNetApplySD3 is marked deprecated and may be removed in future versions. The built-in ControlNet Apply page separately lists both conditioning inputs and outputs and permits outputs to go to another ControlNet or K Sampler, but does not itself state the same sequential-linking behavior. Check the documentation for the node and version in use.
Audit a hypothetical two-control workflow
Suppose a creator wants pose guidance from ControlNet A followed by edge guidance from ControlNet B. The labels and observations below are hypothetical; they show how to audit wiring, not a tested generation or a recommendation for particular control images or strengths.
| Checkpoint | Positive source | Negative source | Expected destination | Audit result |
|---|---|---|---|---|
| ControlNet A input | Text encoder: Base positive | Text encoder: Base negative | A inputs | Both start at the base pair |
| ControlNet A output | A: positive output | A: negative output | ControlNet B inputs | Both continue as a pair |
| ControlNet B input | A: positive output | A: negative output | B inputs | Neither input returns to the base pair |
| ControlNet B output | B: positive output | B: negative output | Sampler inputs | Both final outputs reach matching ports |
For this example, the audit passes only if B’s two input wires visibly originate at A and the sampler’s two wires originate at B. If the sampler’s negative input still comes from Base negative, record a negative-branch bypass even if the positive path is correct.
Diagnose a broken or uncertain chain
If one branch appears to bypass a node, inspect that branch independently from left to right: text-conditioning source, each Apply input, each Apply output, and sampler input. Repair the first incorrect handoff, then trace both branches again; a corrected positive wire does not establish that the negative wire is correct too.
If wiring is paired but behavior is unexpected, check whether the selected node matches the model workflow and whether its required model, image, and VAE inputs are connected. The built-in Apply documentation says ControlNet input images need preprocessing and corresponding ControlNet models must be installed. It does not establish that any particular image, strength, or timing will produce a desired visual result.
The SD3 page marks ControlNetApplySD3 as deprecated and says it may be removed in future versions. Check the node documentation for the ComfyUI version and node you actually use. A connection audit can confirm where conditioning flows; it cannot prove that a pose or edge is correctly represented, or that the sampler will satisfy the creative brief.
Common questions
Should I update negative conditioning at every node?
Yes. The documented Apply inputs and outputs include both positive and negative conditioning. Pass each current output to the matching input of the next node, then send the final pair to the sampler.
Can the next node start from the original text encoders?
Only if that is intentional. If the goal is sequential application, connecting the later node to the original pair bypasses the earlier node’s output for that branch.
How do I detect a positive-only audit?
Read the two conditioning wires separately at every handoff. A valid audit records both the positive and negative source for each Apply input and both destinations for each output. If only the positive wire is traceable, the audit is incomplete; inspect the negative wire through the same checkpoints before accepting the chain.
Sources
Sources and next step
- ControlNetApply - ComfyUI Built-in Node Documentation
- ControlNetApplySD3 - ComfyUI Built-in Node Documentation
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.