ComfyUI Queue & Settings

Monitoring active and completed ComfyUI jobs, and configuring your connection.

These pages let you monitor AI generation jobs and configure how Ordinary Animator connects to ComfyUI.

ComfyUI Settings

Your generation backends are configured in the ComfyUI section of Settings ("Cloud and local connection"), which is the section Settings opens on. It has two blocks, each with its own Enable switch:

Comfy Cloud

  • Paste your Comfy Cloud API key (stored encrypted) and Save
  • Test key verifies the key is valid

Local ComfyUI (localhost)

  • Test local connection checks that local ComfyUI is reachable, and reports which address answered and how it got there -- through the browser extension, or directly if you started ComfyUI with --enable-cors-header
  • When the test finds ComfyUI running but the extension missing, it offers the link to install it

The same section also holds your local models folder and the Files needed list -- see AI Models.

You can have both enabled at once. There is no global "active backend" -- each time you run a workflow you can choose whether that job runs locally or in the cloud. The run may default one way, but you can always override it.

Job Queue

The Comfy Queue page shows all active and recently completed jobs under its Job queue heading:

Column Description
Output Output image preview (when available)
Run Where the job ran -- local or cloud
Status Where the job has got to -- Queued / Rendering / Capturing / Done / Error / Lost, and under it, how recently the row was checked against Comfy
Workflow Workflow name
Start When the job was submitted
Duration Time taken
Cost Credits the job consumed (Comfy Cloud only); these add up by day and month in the Comfy Cloud section of the Costs page
Details What the job was for, and its inputs at a glance
Actions Cancel a running cloud job, or dismiss the row

The open button on a row (or double-clicking the row) takes you to the job's result: if its output landed in a media gallery, you go straight there with that item opened. A single click on the row does nothing. The small info control beside the workflow name opens a Job details window with the full job information -- input parameters, output file links, the job and prompt IDs, and, for a cloud job, the cost broken down into metered GPU seconds and the approximate amount in dollars. The Settings button above the table opens the ComfyUI section of Settings.

How recently a row was checked

Under the status word, an unfinished row says when OA last confirmed it against Comfy itself -- "checked 12s ago". A cloud job's row is not a note OA wrote when you pressed Run and then left alone; it is kept in step with what Comfy is actually holding, whatever page you are on and whether or not the tab you started the job from is still open. You can leave this page open through a batch of renders and watch every row settle by itself.

"not yet checked" means exactly that: the job has been submitted but Comfy has not mentioned it yet. That is normal for a few seconds after you press Run. If a row keeps saying it, or the last check drifts into minutes, something is stopping OA reaching Comfy -- check your connection and, for cloud jobs, your Comfy Cloud API key in settings.

When the connection to your local ComfyUI is lost

A row always says what ComfyUI says, not what OA last assumed. If your local ComfyUI stops while a job is running -- you closed it, it crashed, or the connection dropped -- OA does not leave the row counting on a render that is no longer happening. Within a few seconds every running local job turns to Error with the reason "Lost connection to ComfyUI while this job was running." and one message tells you how many jobs that affected.

When ComfyUI is reachable again, OA re-checks those jobs straight away and puts each one right:

  • Still going in ComfyUI (it was only a network blip): the row goes back to Rendering and finishes normally, and its output lands in the gallery as usual.
  • Finished while OA could not see it: OA collects the result, and the row ends Done.
  • ComfyUI reported its own error: the row shows that error -- which step failed and why.
  • ComfyUI has no memory of it (it was restarted, which clears its list): the row stays in Error and reads "ComfyUI restarted and has no record of this job." Run it again.

This also happens when you open the page after ComfyUI is already back, including for jobs marked Lost.

A row never keeps reading Rendering while ComfyUI is reachable and has no such job.

If you are running in the cloud, a budget line sits above the table: credits used this month against your plan's monthly allowance, the percentage consumed, and when the allowance resets. Dollar figures anywhere in the app are an approximate convenience -- credits are the real billing unit.

Completed and failed jobs from earlier sessions live in the collapsible ComfyUI job history panel at the foot of the ComfyUI settings section, which retains jobs that have scrolled off the active queue.

Cancelling and clearing jobs

Two different things, and the queue keeps them apart on purpose.

Cancel stops a render that is still going, on Comfy Cloud or on your local ComfyUI. Use it the moment you know a run is not worth finishing -- the wrong resolution, or a sibling shot that already came back unusable. Cancelling ends the render where it runs, so a cloud job stops spending credits and either kind stops holding up whatever is behind it in the queue. The button appears only on a job that is still running. A cancelled job reads Cancelled, in a neutral colour; it is never reported as a failure, even though ComfyUI itself files a stopped run under its error status.

Dismiss removes the row and nothing else. It never stops anything, so dismissing a job that is genuinely still rendering simply hides it -- the output still arrives, and the job reappears in the history when it does. Dismiss is for tidying up.

Above the table, Clear finished removes every row that has settled -- done, failed or lost -- in one go. Clear stuck appears only when there is something to clear: a job that has claimed to be running for over an hour. That is the row you get when a workflow is rejected before it starts, and it would otherwise sit there reading "Rendering" for good.

You should need the stuck case less often than you used to. A cloud job that finished while you were on another page is now picked up, saved to the gallery and retired on its own, and a job Comfy Cloud never started is marked as failed with a reason rather than waiting forever.

When the service is busy

Running a whole scene's worth of shots at once is normal, and Ordinary Animator now spaces the submissions out rather than firing them off together. If Comfy Cloud is busy and refuses one, OA waits and tries again -- your job stays queued and you are not told anything, because nothing has gone wrong yet. Only if it keeps refusing do you get a message, and it says the service is busy and to try again shortly.

The same applies while a job is running. Asking Comfy Cloud how a render is doing can fail for reasons that have nothing to do with the render, so a failed check never fails the job: OA waits a little longer and asks again. A job is only reported as failed when Comfy Cloud says it failed.

Watching for new outputs

ComfyUI does not notify Ordinary Animator when a job finishes, so OA finds out by asking it what it has completed. This is Comfy history polling, and it is controlled by the ComfyUI logo button in the media gallery toolbar -- filled in when polling is on, outlined when it is off. It covers whichever backends you have enabled: local, Comfy Cloud, or both.

You rarely need to turn it on yourself. Queueing a job, or copying a workflow to run by hand in ComfyUI, switches polling on for you, so anything you start from OA is collected without a second step. Turn it on manually when a job was started somewhere else entirely and you want its output picked up.

While polling is on, OA checks often at first and then eases off -- roughly every 5 seconds, then every 10, settling to every 30 seconds once nothing new is arriving. A long render is still noticed promptly; an idle session is not checked needlessly.

After 30 minutes with no new jobs, polling switches itself off and tells you it has done so. This is deliberate: an unattended tab would otherwise keep questioning ComfyUI indefinitely. Turn it back on whenever you resume.

Progress under the timer

Once a workflow has run to completion on a backend, the Local | Cloud strip draws a thin line under the running clock, filled according to how far through that workflow's usual time the job is. A job that runs longer than usual simply shows a full line while the clock keeps counting. Stopped, failed and lost jobs never count towards the usual time, and a workflow that has not run yet shows no line.

Status indicators

A job goes through more than "running" and "finished", and the status column says which part it is in. Hover a status for the longer sentence.

  • Queued -- submitted; ComfyUI has not taken it yet
  • Rendering -- ComfyUI is working on it
  • Capturing -- the render has finished and Ordinary Animator is fetching the output and saving it to the gallery. This is a real wait, not a formality: a video can take a couple of minutes to come across, and the Local | Cloud strip at the top of the page keeps showing the job as busy for the whole of it. The job is not finished until this ends
  • Done -- outputs have been fetched and saved to cloud storage, and are in the gallery
  • Error -- the job failed; check the detail modal for the message from ComfyUI
  • Lost -- Ordinary Animator stopped being able to see the render. This is not the same as a failure, and it says nothing about whether ComfyUI finished: a lost job comes back on its own if its output turns up later

A cloud job that Comfy rejected before it ever ran now shows as Error within seconds rather than sitting on Rendering. Comfy is asked two questions at once -- what is in its queue and what is in its history -- and a job in neither is one Comfy never accepted.

The row says why in Comfy's own words wherever Comfy gave a reason. A rejected job usually names the node it would not accept and the input on it, which is the thing you can act on -- change that input and run it again. When Comfy gives no reason at all, the row says what Ordinary Animator was able to establish instead, so you can tell the two apart.

A job that starts and then fails names the node that failed and ComfyUI's own reason, for example "KSamplerAdvanced (node 57) failed: ...", in one line; the row keeps the full detail, including ComfyUI's traceback, in its detail modal. If ComfyUI stops a local job without giving a reason, Ordinary Animator reads the end of ComfyUI's own log and shows what it said there; if that log cannot be read either, the row says so.

A step run from an operation's Run button, or asked for in chat, learns about this too. Such a run is reported as started the moment Comfy accepts the job, so a rejection arrives afterwards; when it does, the run is marked failed with the same reason rather than being left waiting for output that is not coming. If you asked the assistant to run something, it tells you it failed and why instead of saying it is still rendering.

See ComfyUI Integration for how jobs are submitted and how the queue model works.