Sonder Lazy Debug Sleep

Sonder Lazy Debug Sleep is a test instrument, not a feature. It sleeps for seconds, then passes whatever value you gave it through unchanged. That's it. Its whole reason to exist is to make lazy evaluation visible: if a branch of your graph isn't actually running, a node that deliberately wastes time proves it.

Why you'd ever want a sleeping node

Sonder Switch and Sonder Cluster are lazy - they only evaluate the branch you selected, even though every branch is wired to heavy nodes like model loaders, samplers, or video decoders. That's a strong claim, and it's the kind of thing you want to verify before you trust it with an expensive graph. Drop a Debug Sleep (set to a few seconds) inside each branch upstream of a Switch, run the workflow, and watch which branch sleeps.

• If only the selected branch sleeps, laziness works - the others never executed.
• If every branch sleeps, something upstream is defeating the laziness (a non-lazy node forcing evaluation, or a shared dependency both branches need).

The category is even honest about what it is: Sonder/Logic/tests. This is a debug node living in the same pack that ships the lazy switches, and it doubles as a useful "watch me confirm my assumption" toy for anyone learning how ComfyUI's execution model decides what to run. ComfyUI caches aggressively and only re-executes what changed; a sleep node is a crude but extremely legible way to see whether the engine thinks a branch is live.

Inputs and outputs

• seconds - sleep duration, 0 to 60, default 1. Fractional values allowed (step 0.1).
• value - any type. It's passed straight through, so you can thread an IMAGE, a string, a conditioning - anything - through the sleep and keep your graph wired while you probe.

Output is a single value socket carrying whatever you put in.

Install and reality check

It comes with the Sonder pack (ComfyUI Manager search Sonder Editor, or git clone https://github.com/SonderSaid/ComfyUI-Sonder-Editor.git + pip install -r requirements.txt + restart). Like the other lazy nodes it uses ComfyUI's newer V3 node API, so it only appears on a recent ComfyUI build.

The honest framing: don't leave these in a production workflow. A node that sleeps on purpose is the opposite of what you want in a render path, and it's clearly not meant to stay. Use it to confirm the lazy routing, then delete it and wire the real graph. If you're the kind of person who likes knowing why a switch works before trusting it, this is the rare utility node that teaches you something about the engine rather than just doing a job.