Queue Manager Dashboard¶
Once jobs are in the queue, almost everything you do with them — reorder, pause, resume, retry, change priority, edit the frame range, read logs, open the output folder — happens in the Queue Manager dashboard, a page served locally by the queue server and opened in your browser. The Blender N-panel is where you send jobs to the queue and start/stop the server; the dashboard is where you manage them.
Open it with the Open Queue Manager button in the N-panel (only shown while the server is running), or from the Scene Assembler Queue panel in the Render properties tab.
Layout¶
The dashboard has two panes: a job list on the left and a detail pane on the right for whichever job is selected. Drag the divider between them to resize — your choice is remembered, and double-clicking it resets to the default width.
The job list¶
Each job is a card showing its name, status badge, progress bar, and (as the column gets wider) frame count, priority, ETA, and timestamp.
- Filters — All / Running / Queued / Failed / Done, along the top of the list.
- Reorder — drag a card by its handle to move it earlier or later in the queue. This is a manual tiebreak for jobs at the same priority; it doesn't override priority itself (see below).
- Priority spinner — visible on the card once the column is wide enough, and always available in the detail pane. 0–100, 100 = highest.
- Bulk actions — Select All / Deselect All, then Delete Selected, using the checkbox on each card.
- Pause Auto-refresh — freezes the list so you can select log text without it being redrawn out from under you every couple of seconds.
Job statuses¶
| Status | Meaning |
|---|---|
| Queued | Waiting to render |
| Running | Currently rendering |
| Paused | Manually paused, or interrupted by Run Now / a higher-priority job |
| Done | Rendered successfully |
| Failed | Render process exited with an error, or was stopped |
The detail pane¶
Click a job to see:
- Overall progress — percentage, frames done / total, and ETA while running.
- Layers — one row per view layer for a multi-layer job (see Sending Jobs for when a job shows one combined row instead of several).
- Frame Range — see below.
- Actions — buttons appropriate to the job's current status (see below).
- Recent Log / Full Log tabs — Recent Log is a running log of what the render script reported (layer starts, frames rendered, saved files); Full Log is the raw Blender console output.
Job actions¶
What's available depends on status:
- Run Now (queued or paused jobs, while something else is rendering) — pauses whatever's currently running and starts this job immediately.
- Pause (running) — suspends the render process. It stays paused until you resume it.
- Resume (paused) — picks the job back up. An animation resumes from the last frame it actually finished rendering, not from the beginning.
- Stop (running) — cancels the job and marks it Failed.
- Restart from last frame (failed, animation only) — re-queues the job starting from the last completed frame instead of redoing the whole render.
- Restart from start (failed) — re-queues the job from frame 1 (or the job's start frame).
- Remove — deletes the job from the queue list.
Every job also has Open Output (opens the render output folder) and, once it's finished or failed, View Log (opens the full render log in your text editor).
Frame range¶
For an animation job that's queued, paused, or failed, the Frame Range section in the detail pane lets you change its start and end frame before it runs (or runs again):
- It defaults to whatever Blender submitted — shown as "As submitted from Blender" until you change it.
- Once you set a different range, a Reset button appears to put it back.
- Extending the end frame keeps whatever progress the job already made — it picks up from the same frame it would have anyway, just with a longer run ahead of it.
- Moving the start frame past where the job had gotten to, or the end frame below it, clears that progress — the job renders the range you just asked for from its new start, rather than trying to resume into a range that no longer makes sense.
A running job shows its frame range read-only (stop it first to change it); a finished job's range can no longer be edited.
This is the fastest way to finish an interrupted render on a sub-range, or trim an animation down, without re-submitting a whole new job from the node graph.
Priority and preemption¶
Every job has a priority from 0–100 (default 50, set when it's submitted — see Sending Jobs). Among queued jobs, the highest priority renders next; ties fall back to queue order.
If you raise a queued job's priority above the one currently rendering (or add/resume one with a higher priority), the running job gets pushed aside. How that happens is controlled by a preference, Edit → Preferences → Add-ons → Scene Assembler → Priority Preemption:
- Stop Immediately (default) — the running render is stopped right away and resumes from its last completed frame once it's picked up again.
- Wait for Current Frame — lets the running render finish the frame it's on first, then pauses, so that frame's work isn't repeated.
Either way, the preempted job goes back into the queue automatically — you don't need to manually resume it.
Auto-retry¶
See Auto-Retry for the full picture — retried jobs show up here the same as any other, going back to Queued with a log note about the retry attempt.
Convert to Video¶
A job that has a Convert to Video node attached shows an extra row in the Layers table for the conversion step, tracking through pending → converting → done (or failed/skipped) alongside the render itself.
Completion webhook¶
Edit → Preferences → Add-ons → Scene Assembler → Completion Webhook can POST a notification to a URL (e.g. a Discord or Slack webhook) whenever a job finishes or fails — useful for long unattended render sessions where you're not watching the dashboard.