2.Grok 查询状态 (Wujiai)

Middle child of the Wujiai Grok video flow: 1. GrokSubmitTask → 2. GrokQueryTasks → 3. GrokGetNextVideo. The submit node fires a job off into the Wujiai cloud; this node asks "did it finish?"; the download node grabs the result. GrokQueryTasks is the status-checker, and it's the one you'll want to run on a loop (or re-run manually until the report shows the task is done).

It's a deliberately boring node, and boring is the point. Zero required inputs, one optional api_key field, one report STRING output. You feed it the key (or leave it blank and let the pack fall back to WUJIAI_KEY / the ApiKeyManager), run it, and read a text summary of your task states.

What the report actually tells you

The report is a plain-text ledger of the tasks the Wujiai channel knows about - submitted, running, succeeded, failed, downloaded. In practice you're looking for one thing: whether your GrokSubmitTask job has flipped from "processing" to a state where GrokGetNextVideo can pull it. Because the query and the download are separate nodes, a common beginner loop is: run query, see "succeeded", run get-next-video, done. If you skip straight to download without querying, you may hit an empty pipe.

How it fits

This whole flow is the "enterprise async task management" pattern the pack advertises in its README: submit, persist, poll, download. On the Grsai side the same shape exists with a local task database (a thread-safe TaskManager writing JSON under data/), so tasks survive restarts. The Wujiai Grok nodes follow the same submit→query→download rhythm, though here the task registry lives server-side on the Wujiai channel rather than in a local JSON file. Either way: don't expect the query node to download anything, and don't expect the submit node to wait. Each node owns exactly one step.

Install & usage

Same pack install as everything here:

cd ComfyUI/custom_nodes
git clone https://github.com/jieg9341-lab/ComfyUI-nkxx

then restart (or use ComfyUI Manager, search "ComfyUI-nkxx"). First launch auto-installs requests, pandas, openpyxl, yt-dlp, opencv-python, aiohttp. No models, no VRAM - the query just phones the Wujiai API.

You need a Wujiai key (wujiai.org registration link is in the README). This node only reads status, so unlike the submit node it doesn't burn credits by itself - but every query hit against a still-running job is just a status check, not a render.

Common issues

• "No tasks found" after a submit: either the submit actually failed (check its response), or you're looking at a different channel. Grok video tasks live under the Wujiai key, not a Grsai key - mixing keys across nodes in the same flow is the number one way to get an empty report.
• Task stuck "running" forever: the Wujiai side owns the queue, so the fix is usually waiting or re-submitting, not re-querying harder. A failed render will eventually show as failed in the report.
• Trust note, same as the rest of the Wujiai side: the node's source is obfuscated in the shipped files, so "what does this query actually send" is only verifiable by behavior. Fine for a status check; keep it in mind anyway.