ComfyUI Queue & Settings

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 Job Queue page shows all active and recently completed jobs:

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
Workflow	Workflow name
Start	When the job was submitted
Duration	Time taken
Cost	Credits the job consumed (Comfy Cloud only)
Details	What the job was for, and its inputs at a glance

Clicking a row takes you to the job's result: if its output landed in a media gallery, you go straight there with that item highlighted. When there is no output to go to, the row opens a detail modal instead, 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.

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.

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.

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 queue count in the avatar badge stays lit 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

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