⏰Time Sleep

pc time sleep (⏰Time Sleep) is the odd one out in the ComfyUI-PC-ding-dong pack: it makes no sound at all. All it does is pause execution for a number of seconds. That's the entire job, and it's honest about it - one input, one output, no mystery.

Why you'd reach for it

This pack is a notification toolkit, and Time Sleep is the pacing utility that ships alongside the bells. You'd use it when you want a deliberate pause in the middle of a run: give an API-backed workflow a beat between calls, slow down a batch loop so you don't hammer an endpoint, or insert a "let that settle" moment before the next stage. It's also handy as a crude debug stop - run up to a point, wait, watch what happens. None of this is glamorous, which is fine. It's a utility, and utilities don't need to be.

How it works

The mechanism is gloriously blunt: the node calls time.sleep(seconds) on the execution thread. That means the whole queue stops, not just one branch - everything queued behind it waits for the timer to elapse. That's also why the input is capped at ten seconds: the author knows this is a sledgehammer, so they gave it a short swing. If you need a real 90-second delay, chain a few of these or use a proper scheduling setup; this node is for short, deliberate pauses.

Inputs and output

• seconds - FLOAT, 0–10, default 1, step 0.1. The only thing you'll ever set.
• anything - optional this time, unlike the pack's other nodes. It's an any-type passthrough: wire in a model, image, latent or string and it comes back out output untouched. Leave it unconnected and the node just sleeps.

The output, output, is that pass-through. The node is marked as an output node, so you can also park it at the end of a workflow as a checkpoint that says "this is where the run pauses."

Installing it

Same pack, same install. ComfyUI Manager → search ComfyUI-PC-ding-dong, or:

cd ComfyUI/custom_nodes
git clone https://github.com/lgldlk/ComfyUI-PC-ding-dong

Then restart ComfyUI. No dependencies, no model files - this pack has neither, which is rare and nice.

The one real gotcha

Remember the whole-queue thing. If you drop a 10-second sleep mid-graph while several jobs are queued, they all pile up behind it - a long batch with one of these in the loop can quietly turn a 20-minute run into a 40-minute one. Keep pauses short and deliberate, and treat the 10-second cap as a feature, not a bug. There's no API-throttling magic here; it's a pause button, and sometimes that's exactly what you needed.