Files
malkuthro-ComfyUI-Koolook/docs/user_guide/nodes/koolook_loop/koolook_loop_status.md
T
malkuthro 30d51cf365 fix(loop): harden Koolook_LoopStatus auto-queue (#241)
Auto server_url detection (widget defaults to 'auto'); the connected index wire is authoritative for frame-index detection (a stale numeric label no longer overrides it); fold in #207 (string-bool auto_queue_next + detected index-node logging); review hardening (IPv6 / bare --listen, Bandit B104, blank server_url, debug diagnostics).
2026-06-18 18:16:08 +02:00

2.8 KiB

Koolook Loop Status

Field Value
Source Koolook-native
Node ID Koolook_LoopStatus
Display name Koolook Loop Status
Category Koolook/Loop

Koolook_LoopStatus is a pass-through loop status node. It prints progress such as EXR_SAFE: 1/4 frame 0 -> path/to/frame.0000.exr, returns the input value unchanged, and can queue the next prompt by advancing a connected easy int frame-index node.

Use it when a workflow must process one frame per ComfyUI execution instead of passing a whole image sequence through a deep subgraph. The frame-index node drives ImageFromBatch.batch_index and the saver frame number. Queue the graph once at frame 0; with auto_queue_next enabled, the status node submits the next prompt until index + 1 == total.

Key inputs:

  • value: the image, latent, or other payload to pass through.
  • index: current zero-based frame index.
  • total: total number of frames to run.
  • filepath: optional sequence path used only for the printed status line.
  • label: status label, for example EXR_SAFE.
  • auto_queue_next: when enabled, submit the next prompt automatically.
  • index_node_id: advanced override for the connected easy int frame-index node — leave it blank for normal use. The node infers the frame-index node from the connected index input and logs the detected node class/id when it queues the next frame. If a saved workflow carries a stale manual id (e.g. a widget value shifted to 0), the connected index input is used instead so the loop self-heals; if it still cannot resolve a real node, auto-queue fails up front with a clear message instead of silently aborting into a marker file.
  • server_url: where to queue the next prompt. Defaults to auto, which detects the running ComfyUI server (its real port included) — so an install launched with --port 8000 queues correctly without editing the widget. Leave it at auto (or blank) for normal use; set an explicit http://host:port only to target a different server, where it is used verbatim.
  • max_auto_queue_depth: hard safety cap for how many child prompts this node may chain from the current frame.
  • remaining_auto_queue_depth: internal countdown carried into child prompts. Leave this at -1 in normal canvas use.

If an older saved workflow accidentally shifts widget values and puts a numeric node id into label, the node resets the label to EXR_SAFE and keeps that number only as a last-resort fallback frame-index id — the connected index input still wins, so the loop follows the wiring deterministically (you do not need to clear the label by hand). This keeps older loop demo saves from crashing, but new workflows should set label explicitly and leave index_node_id blank unless there is a specific override reason.