Beeble Poll Job Test

Somewhere between "I started a job" and "the render is ready" sits this node. Beeble Poll Job Test does a single status check on a Beeble job: give it a job_id, get back the current status, a progress number, and the full JSON response. It queries once and returns - it does not loop, does not wait, does not block your workflow.

That's the defining thing about this node, and the reason it exists as a separate test step. The production nodes use wait_for_job, which polls in a loop until completion. This node is the raw, one-shot version so you can watch a job's lifecycle with your own eyes: start a job, poll it every now and then, and see statuses move from whatever Beeble reports (queued-ish states, processing, completed) toward done. If you're debugging why a job fails, seeing the status and the raw payload at the moment of failure tells you far more than the production node's terse "generation failed" message.

How it works

A GET /v1/switchx/generations/{job_id} with your key in the header, the same retry-once-twice network handling as everything else in this pack. Terminal statuses are completed, failed, and cancelled - anything else means it's still cooking. The progress field is whatever Beeble reports (a float, often 0 for statuses that don't carry progress), so don't expect a smooth 0→100 bar; treat it as informational.

Inputs and outputs

• job_id (STRING) - required. Grab it from the Start Image/Video Generation Test nodes, or from the job_id output of a production node's logs.
• status (STRING) - the job's current status, human-readable.
• progress (FLOAT) - Beeble's reported progress.
• status_json (STRING) - the full raw payload, for when you actually need to know what Beeble thinks is happening.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/albert999-pixel/comfyui-beeble-switchx.git

Or search Beeble in ComfyUI Manager, restart, and set BEEBLE_API_KEY via .env in the node folder, an env var, or ComfyUI Desktop's env-variables panel. No extra dependencies - empty requirements.txt, no models to download.

Common issues

• Empty job_id - the node raises "job_id is required." The field's default is an empty string, so it's easy to run it before wiring anything in.
• 401 / key error - the key is the same one everything else uses; validate with Account Info Test.
• Polling shows the same status forever - video jobs can sit in processing for minutes. That's normal for the expensive ones; if it never moves past that within your patience, check status_json for an embedded error.
• You actually wanted to wait - use the Wait Job Test node instead, which loops for you.