Queue Manager Overview¶
Scene Assembler includes a local render queue that runs Blender in the background. You can send jobs while you keep working, then monitor progress, reorder jobs, and handle failures from the Queue Manager dashboard.
How it works¶
When you send a job to the queue, Scene Assembler:
- Evaluates the node graph to determine what to render
- Assembles a temporary render scene in a copy of your .blend file
- Sends the job to the queue server (a lightweight local process)
- The server launches Blender in background mode to render the job
- When the render finishes, the next queued job starts automatically
The queue server runs as a background process and persists between Blender sessions, so renders can continue even if you close Blender (as long as the machine stays on).
The N-panel¶
Open the N-panel in the Scene Assembler node editor by pressing N. The queue section shows:
- Available jobs — Scene nodes in the current graph (or all graphs if All Trees is on) that can be sent to the queue
- Job counts — how many jobs are running, queued, done, and failed
- Batch list — a saved list of jobs you want to render together
- Start Server / Stop Server and Open Queue Manager
The N-panel is where jobs get submitted. Once they're in the queue, monitoring progress, reordering, pausing/resuming, changing priority, editing the frame range, and reading logs all happen in the Queue Manager dashboard — see Managing Jobs.
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 |
Starting and stopping the queue¶
Start Server — launches the queue server if it isn't running. The server also starts automatically the first time you send a job while it's stopped.
Stop Server — stops the queue server. Any running job is interrupted and set to Paused.