Deadline Seed

If you open an old saved workflow and find a DeadlineDistributedSeed node staring at you, don't panic - it's the same node as DeadlineSeed wearing a retro name. In the current pack it's registered as a deprecated alias: same display name ("Deadline Seed"), same inputs, same output, same behavior. ComfyUI flags it as deprecated in the UI, but it loads and runs fine. It exists so that workflows built against an older version of the plugin don't shatter the moment you update.

Why it exists

There was an earlier plugin in this space (ComfyUI-Deadline-Distributed) with a different approach - it exposed fake /deadline/* HTTP routes and a distributed-seed concept built around those. This pack folded the useful part of that idea into a single seed node and dropped the route hack entirely. The README is blunt about it: the old fake API routes are gone, and ComfyUI-Deadline-Distributed owns its own routes if you're still running that. The DeadlineDistributedSeed class name is the compatibility shim so a graph saved during that era keeps resolving to something real.

What it does

Exactly what DeadlineSeed does - it's a subclass, not a parallel implementation. One INT input (seed), one INT output (seed). Locally it passes the seed through unchanged; on the farm, hidden values injected by the Deadline worker plugin make it vary per variation in batch mode (seed + task_id) or per worker in distributed mode (seed + worker_index + 1). Same 0-to-1125899906842624 range, same big default. If you're choosing which node to drag into a new graph, use DeadlineSeed - the deprecated flag exists so new builds don't pile up more legacy.

Install and wiring

Same pack, same one-liner - clone doubletwisted/ComfyUI-Deadline-Plugin into custom_nodes (or find "ComfyUI Deadline Submission" in ComfyUI Manager), restart, then deploy the Deadline-side plugin with the pack's PowerShell script. No extra Python dependencies. Wire it exactly like any seed node: seed value in, seed out to the KSampler.

The whole reason this node is on the page at all is backwards compatibility. If a saved workflow loads it, leave it and it'll render identically. If you're starting fresh, reach for DeadlineSeed and don't look back.