PrimitiveDelay

This one is exactly what it looks like: a time.sleep() wearing a node costume. PrimitiveDelay pauses execution for however many seconds you ask, then passes its input through untouched. There's no clever memory management, no audio math, no model loading - the pack's README doesn't even bother describing it, because there's nothing to describe.

So why does it exist in a suite built around heavy sequential video renders? Pacing. When your graph re-queues itself hundreds of times in a row, you sometimes want a beat between cycles: let a hot GPU cool down, wait for an external service to finish writing a file, give a download time to complete before a node reads it. The pack's own tooltips are honest about the job - "pause time in seconds" on the input, "connect the wire you want to delay" on the passthrough.

How it works

Execution reaches the node, it sleeps for delay_seconds (0 to 3600, default 1, steps of 0.1), prints a log line before and after, and returns whatever any_in it was handed. That passthrough is the actual design: you don't use this node to produce anything. You insert it inline on a dependency so that the downstream node physically cannot execute until the delay elapses. Put it before your stitcher and the whole assembly waits; put it on a control wire and only that branch waits.

Inputs and outputs

• delay_seconds (FLOAT) - the pause length. Default 1; 3600 is a full hour if you're feeling ambitious.
• any_in (optional, any type) - the wire to delay.

Output is a single passthrough output of the same type you fed in. Because the input type is *, you can hang this node anywhere without fighting type mismatches.

Installing it

It's bundled in comfyui-sequential-batcher:

cd ComfyUI/custom_nodes
git clone https://github.com/Meisoftcoltd/comfyui-sequential-batcher

or ComfyUI Manager, search "comfyui-sequential-batcher", restart. Zero extra dependencies - it's a stdlib time import.

Common issues

The honest warning: this node blocks the whole execution thread, not just its own branch. A long delay (minutes) will stall ComfyUI's worker and queue anything else behind it - a 300-second sleep looks like a frozen server to anyone watching. Keep delays short (a few seconds) and use it sparingly. If you're tempted to use it for "cooling" a card mid-render, reconsider: the pack's own VRAM Defragmenter is the tool that's supposed to handle that, and a sleep won't unload anything by itself.