Wait Seconds 🐲

Yes, this is a node that sleeps for a set number of seconds and then passes your image through unchanged. It sounds absurd until you've been bitten by a rate limit mid-batch, or you're hammering an external service and you need ComfyUI to not fire off ten jobs at once. Then a node that deliberately stops the queue feels like a feature.

What it does

Ryuu_WaitNode takes an IMAGE and an integer seconds (0 to 60, default 10), sleeps for that long, and hands the image back exactly as it came in. The only real output is the delay itself.

The implementation is dead simple: a time.sleep() loop in 10 ms steps while it updates ComfyUI's progress bar, so you get a live countdown on the node instead of staring at a frozen graph wondering if it hung. If seconds is 0 it skips the sleep entirely and passes straight through. That's the whole node.

Why you'd actually use it

• Rate limiting - if you're chaining into an API (image-to-text, a hosted service, whatever), a pause node keeps you under per-minute limits without babysitting the queue.
• GPU cooldown / sequencing - a short pause between heavy jobs on a hot card, or between encode/decode passes that thrash VRAM.
• Staggering saves - if a downstream script watches your output folder, a delay keeps it from tripping over itself.

It's a utility you'll reach for rarely but be glad exists. The author made this pack "mainly for personal use," and this is the most personal-use node in it. Don't overthink it.

The inputs

• images - an IMAGE. Required, because a pass-through node needs something to pass. Wire whatever image is flowing through your graph.
• seconds - 0-60, default 10.

Output is a single IMAGE - exactly the input, untouched. You can drop it mid-wire without changing anything downstream except the timing.

Installing it

Same pack install as every RyuuNoodles node:

cd ComfyUI/custom_nodes
git clone https://github.com/DraconicDragon/ComfyUI-RyuuNoodles

Then restart ComfyUI. Or use ComfyUI Manager and search "RyuuNoodles". No model files, no extra heavy dependencies.

Gotchas

The sleep is synchronous - it blocks the whole execution queue for the duration. If you're running multiple jobs in parallel with --multi-user or chained queues, one Wait node stalls everything, not just its own branch. Keep waits short (it maxes at 60 seconds anyway) and be aware that the node is marked experimental in the code, so it's a "works for me" utility rather than a polished one.