ComfyUI Queue

This screen has no nav entry; reach it by typing /queue. The route works and is live — its entry in the global nav is commented out, not deleted.

It answers one question: what is ComfyUI doing this second. Two lists, both refetched every five seconds while the page is open — jobs that are running, and jobs that are queued waiting for a slot. Nothing else appears here, so a job that has not been dispatched yet, or that finished a minute ago, is not on this page. The subtitle under the heading gives you the two numbers at a glance: "N currently processing, M queued".

Everything on this page is monitoring. Queueing and re-queueing happen on Jobs — and nothing anywhere in the app cancels a generation that is already running. Once ComfyUI has picked a job up, the only way to stop it is in ComfyUI itself.

What is on this screen

Currently Processing

One card per running job. The whole section disappears when nothing is running — an idle ComfyUI leaves you looking at Queued Jobs with no explanation above it, which is the page working correctly, not a failure to load.

Each card carries:

• the job id, and a spinner while it is processing
• a source tag in the form platform / handle — reddit / gonewild, instagram / someuser. It is not the r/ or @ form used elsewhere in the app, and a Telegram job shows the bare word telegram with no handle.
• the trim range as MM:SS–MM:SS, taken from the job's segment
• a PROCESSING badge. It is the only badge this page can show — every card in the section is stamped processing regardless of what ComfyUI reports internally, so the badge tells you the section you are in, not the stage the job is at. For per-stage detail, open the job on Jobs.

Where a thumbnail would go you may instead see Preview unavailable / Waiting for a durable image. That is a job whose preview still points at a temporary source rather than a stored image; it resolves on its own once the durable copy exists, and it says nothing about the health of the generation.

Queued Jobs

The queued backlog, newest first, as a grid of video cards with a Search queued jobs... box above it. The search filters the cards already on the page by subreddit, username, or post title — it is a client-side narrowing of the queued list, and it never reaches the running list or anything outside the queue.

Both lists are capped at fifty jobs each and exclude archived ones. A deeper backlog than that is not visible here; the Running tab on Jobs is the place to page through it.

The buttons on a queued card do nothing

Each queued card renders Play and Archive in its hover overlay, and its footer shows the usual media-card links. None of them are wired on this screen. They come from the shared media-card component and this route passes no handlers, so pressing them is silent — no error, no effect. The footer links are built for the media gallery and are constructed from the job id here, so they do not resolve either.

To actually act on something you see on this page, go to Jobs. The Currently Processing card has a cancel affordance in its component, but this route never supplies the handler, so no cancel button renders here either — and there is none on Jobs to fall back to.

How jobs get here and where they go

A job reaches this page when it is dispatched to ComfyUI — Queue to ComfyUI on a captioned job, Re-queue to ComfyUI on a failed one, or the nightly automation window seeding generation on its own. It appears under Queued Jobs first, moves to Currently Processing when ComfyUI picks it up, and drops off the page entirely when it lands on completed or failed.

On Jobs, both halves of this page sit under a single Running tab, which is the queued and running statuses together. This screen is the version that separates them.