Managing Jobs

Job controls

Each job in the queue panel has controls for managing its state:

Run Now — moves this job to the front of the queue and starts rendering it immediately. If another job is currently rendering, it is paused and queued behind this one. The paused job can be resumed normally.

Pause / Resume — pauses a queued or running job. A paused job does not render until resumed.

Cancel — removes the job from the queue. If the job is currently rendering, the render process is stopped.

Retry — re-queues a failed job for another render attempt.

Reordering jobs

Drag jobs up and down in the queue to change their render order. The topmost queued job renders next.

Priority

Jobs are rendered in queue order. Use Run Now to jump a specific job to the front without reordering the rest of the queue.

Clearing the queue

Clear Done — removes all completed jobs from the queue list.

Clear All — removes all jobs (except currently running ones).

Monitoring progress

The queue panel shows:

• Which job is currently rendering
• Progress percentage and current frame (for animation jobs)
• ETA — estimated time until the current job completes, based on per-frame render times
• Error messages for failed jobs

Multi-layer jobs: one row, or several?

A job built from a Scene node with several View Layer nodes connected shows differently depending on how it was submitted (see Sending Jobs):

• Grouped or separate jobs show a LAYERS section (or separate cards) with one progress row per view layer.
• A merged job — where the layers share camera/world/render settings and render together as native view layers on one shared scene — shows as a single combined progress row instead. This is intentional, not a missing feature: Blender renders every view layer of that scene together in one pass per frame, so there is no finer unit than "the frame" to report progress or retry against. Auto-retry for a merged job resumes from the last completed frame, exactly as it does for a single-layer job.