Flux Finetune Status (BFL)

Flux Finetune Status (BFL) answers one question: is my finetune done yet? When you train a custom Flux model on BFL's cloud (or kick off a finetuned generation with one of the finetune nodes in this pack), it doesn't finish instantly - it runs as an async task you poll. This node takes a finetune_id and returns the current status as JSON: pending, generating, ready, error, that whole timeline.

It's the status-check half of the ComfyUI-FLUX-BFL-API pack's finetune console. Where Flux My Finetunes lists your models and Flux Finetune Details gives you a model's full metadata, this one tells you where a specific training or generation job currently sits. Useful in the same way a "build status" page is useful: when you're watching a long training run and want to know if it's stuck, done, or dead.

How it works

It's a GET to get_result with your finetune ID as the query parameter - the same polling endpoint the generation nodes use, just called once on demand instead of looped. The response JSON (status, progress, and result data once complete) comes out the STRING output, pretty-printed. The node also logs the status to the ComfyUI console so it's visible mid-queue.

The inputs and output

• finetune_id - the ID of the finetune or finetuned-generation task you're checking. You'll typically grab it from Flux My Finetunes or from the console logs of the node that kicked the job off.
• config (optional) - a Flux Config (BFL) node with the region set. This is the finetune-section rule: the default api.bfl.ai/v1/ doesn't serve finetune routes; you need us or eu.
• Output: STRING - the JSON status blob.

Installing it

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/gelasdev/ComfyUI-FLUX-BFL-API.git

Restart, key set, region set on your config node. torch is the only declared dependency.

Where people get burned

• Region again. Every finetune node in this pack fails without the region set on a Flux Config (BFL) node. If status calls error, that's the first thing to check.
• Pasting the wrong ID. This endpoint returns whatever the API says about that ID - including a "Task not found" style response if you typo'd it or grabbed a generation task ID instead of a finetune ID.
• Expecting a finished image out. This node returns status JSON, not images. When status says Ready, the result field in the JSON carries the payload - and if you wanted the generated image itself, that's the finetuned generation node's job, not this one's.

Pair it with Flux My Finetunes and you've got the complete "did it work" loop for hosted training. It's not glamorous, but when a two-hour finetune is running, this is the node that saves you from refreshing the dashboard.