PoYo Get Job Status

Some nodes are tools, and some are just a way to ask a question. PoYo_GetJobStatus is the question-asker: give it a task_id and it makes exactly one call to PoYo's status endpoint, then hands you back where the job stands. It doesn't poll, it doesn't wait, it doesn't loop. One snapshot, no commitment.

This is the lightweight sibling of PoYo_AwaitJob. Where AwaitJob sits in a loop until a job finishes or dies, GetJobStatus is for when you want to know the state of a task without blocking your workflow on it - checking whether a background job you submitted earlier is done, inspecting a result, or just probing before deciding what to do next. Because it's one call, it's also the cheapest node in the pack to throw into a graph; it won't sit there hammering an endpoint.

Mechanism. Feed it a task_id (STRING, the only input it takes) and it hits GET /api/generate/status/{task_id} once and returns. PoYo's statuses pass through untouched: not_started, running, finished, or failed. No retry-and-wait logic here - the HTTP client does its normal retry/backoff on network hiccups, but the node itself makes a single query.

Outputs. Four STRINGs, all slices of the same status response:

• status - the current state of the task.
• files_json - the result files as a JSON array, once the job has produced any.
• output_json - the model's structured output.
• response_json - the full raw response, for when you want everything.

In a typical graph you'd take status into a logic or switch node to branch on whether the job is done, then pass files_json on to something like the Save Result File node when it is.

Install. It's part of the poyo-comfyui pack. That needs ComfyUI 0.32.0+ (native node system). ComfyUI Manager (search "PoYo"), comfy node install poyo-nodes, or:

cd ComfyUI/custom_nodes
git clone https://github.com/PoyoAPI/poyo-comfyui.git

then restart. No models to download; nothing heavy.

The honest caveat. Because it queries once, you get a snapshot that can be stale by the time you use it - a running status can be finished a second later, and there's no way to tell from the node itself. For anything where the workflow actually needs to block on completion, reach for PoYo_AwaitJob instead. Also remember the key setup applies here like everywhere in this pack: POYO_API_KEY in your environment, or python -m poyo_nodes.configure to write ~/.poyo/comfyui.json - the node needs credentials even for a status check.