easy sleep

easy sleep does exactly what the name says: it holds up execution for a number of seconds, then passes whatever came in straight through. It's a deliberate delay you can drop into the middle of a graph. Niche, but when you need it there's no clean alternative - pacing calls to a rate-limited API, giving a slow disk write time to land before the next node reads it, or just staggering steps in an automated loop so you're not hammering something.

It's a pass-through, so it doesn't change your data at all. It only changes when the downstream nodes run.

How it works

The node accepts a value on any, waits for delay seconds, then emits that same value on out. Because ComfyUI executes a node only when its inputs are ready, inserting easy sleep on a wire forces everything downstream of it to wait the full delay before it fires. The value is untouched - it's purely a timing device. Put it between two stages and you've inserted a guaranteed gap between them.

The inputs and output

• any - the value to pass through. It's a wildcard type, so anything works: an image, a latent, a string, a pipe. The node doesn't care what it's carrying.
• delay - seconds to wait, defaulting to 1. Fractional values are fine (0.5 for half a second); the range goes absurdly high if you ever want a long hold.
• Output: out - the same value, released after the delay.

How to install it

Via ComfyUI Manager: search "ComfyUI Easy Use", install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

Then install.bat / pip install -r requirements.txt, restart. Preinstalled on comfy.icu.

Common issues

The thing to be clear-eyed about: a sleep is dead time. On a serverless or metered GPU setup, seconds spent sleeping are seconds you may be paying for, because the machine is up and idle rather than doing work. Use the smallest delay that solves your problem, and don't leave a generous "just in case" sleep in a workflow you run at volume - it adds up.

Second, easy sleep gates only the branch it's wired into. ComfyUI runs independent branches as their inputs become ready, so a sleep on one wire doesn't necessarily pause the whole graph - parallel branches can keep going. If you need everything to wait, the sleep has to sit on the wire that feeds the thing you actually want delayed. And if you're using it to wait for some external side effect to finish, remember it's a fixed timer, not a "wait until done" check - if the external thing takes longer than your delay, you'll race it anyway. For that, a real existence check like easy isFileExist is the sturdier tool.