Queue on remote (end of chain)

This is the node people forget when they build ComfyUI_NetDist's "advanced" multi-GPU chain for the first time - it doesn't do anything visually exciting, so it's tempting to skip. Don't: RemoteChainEnd is what actually closes the chain that RemoteChainStart opened and however many RemoteQueueWorker nodes extended, and without it the remote_chain just dead-ends with nothing to show for it.

Same pack, same author - city96, the ComfyUI-GGUF person, going back to his earlier, unrelated distributed-execution project. The whole chain pattern exists for setups with more than two GPUs, where RemoteQueueSimple alone doesn't give you enough per-machine control.

How it works

By the time a remote_chain token reaches this node, it's carried the workflow and settings through RemoteChainStart and every RemoteQueueWorker along the way, each one having forwarded a job to its own remote machine. RemoteChainEnd takes that final token and returns the same two values RemoteQueueSimple hands you directly in the simpler setup - the seed and batch that actually ran - just at the end of a multi-hop chain instead of from one all-in-one node.

The inputs and outputs that matter

• remote_chain (REMCHAIN, required) - the only input. It has to come from the chain; there's no other way to produce this type.

Outputs: seed and batch (both INT) - what the whole chained run actually used, useful if you want to log or react to it downstream, the same pair RemoteQueueSimple exposes on its own.

How to install it

Via ComfyUI Manager: search ComfyUI_NetDist. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/city96/ComfyUI_NetDist
pip install requests

Restart ComfyUI. requests is the only dependency for the whole pack.

Common issues & troubleshooting

Nothing happens when you queue. Check every link actually got wired: RemoteChainStart into the first worker, each worker into the next, and finally into this node. A dangling remote_chain connection anywhere in that line breaks the whole thing without a loud error.

Chain built correctly but still doesn't run. Same footgun that hits the rest of this advanced pattern - the README notes it "needs a fake image input to trigger," since nothing in the chain is an IMAGE type ComfyUI would otherwise execute on its own. Wire a dummy image in somewhere upstream to force the branch to fire.

You built the chain but skipped this node. It's easy to assume the last RemoteQueueWorker is the end of the line since it's doing the visible work - it isn't. Without RemoteChainEnd, the chain has no defined finish and no seed/batch output to show for the run.