Cooldown -INT-

Cooldown -INT- is the number-flavored member of the Cooldown pack: feed it an integer, it waits, it hands the same integer back. The whole node is six lines of Python, and the heavy lifting is time.sleep(). If you've ever wanted your graph to hit the brakes for a beat - on purpose - this is how.

What's an INT in a ComfyUI graph? Seeds, batch sizes, step counts, fixed denoise values, resolution numbers... any of the little numeric wires that thread through a workflow. The cooldown doesn't care what the number means; it just parks it for a while.

Why you'd reach for it. The most useful pattern is pacing a loop. When you run a workflow with a batch count or a repeat-style loop, generations dump out back-to-back in one burst. Drop a cooldown into the numeric path between iterations and each one gets breathing room instead. Same story if you're driving ComfyUI from an API and want to throttle how fast jobs land. And there's a simpler reading, too: it's a pause button. Set sleep to 30 and the graph sits there for half a minute before continuing.

How it works - straight from the source:

def main(self, INT, sleep):
    time.sleep(sleep)
    return (INT,)

No arithmetic, no state, no callback. Sleep, then return the value untouched.

The inputs (both required):

• INT - the number to hold. It's marked forceInput, so it has to be wired from another node; you can't type a value inline. That's deliberate: this node is meant to sit in the middle of a live wire, not at the end of one.
• sleep - the delay in seconds. Default 1, min 0, max 300 (five minutes).

The output is one INT, same value. The node is flagged as an output node so ComfyUI reports the result, but you'll usually just wire it onward into whatever the number feeds.

Gotchas. Same family as the rest of the pack: the sleep blocks execution. While the node waits, its queue slot is taken, so don't use this to "schedule" work on a busy backend - use it to pace. The cap is 300 seconds; if you need a longer pause, chain two nodes. And sleep of 0 is a legal no-op, which turns the node into a pure passthrough - handy as a breakpoint. Drop it onto a wire to confirm data is flowing, then crank the sleep back up.

One thing people assume that isn't true: there's no actual "cooldown state." The node doesn't remember a last-run time or enforce a minimum gap between executions - it's not a throttle that tracks history. Every execution simply waits sleep seconds, always. That's the feature, and it's also the limitation.

Install. ComfyUI Manager is easiest - search for "ComfyUI Cooldown Node", install, restart. Or clone manually:

cd ComfyUI/custom_nodes
git clone https://github.com/tuki0918/ComfyUI_Cooldown_Node

Restart and you'll find Cooldown -INT- (and its siblings) under the Cooldown category. No requirements.txt, no model files, nothing to download. It won't show up in workflow-share threads and nobody's posting about it on Reddit - it's the kind of node you only discover by searching when you need it. For a quiet one-trick utility, that's fine; it does the one trick honestly and leaves your environment alone.