Inspect a render job

The job page is a resizable workspace. Collapse or resize panels to fit the task: visual review, frame diagnosis, settings checks, or performance analysis.

*Resize or collapse the workspace panels around the current review or diagnostic task.*

• Annotation 1: Job status, progress, and actions

• Annotation 2: Selected-frame details and re-render

• Annotation 3: Frame grid

• Annotation 4: Sequence preview

• Annotation 5: Job and scene details

• Annotation 6: Operations chart and render logs

Workspace panels

The browser remembers panel sizes and collapsed state. If a panel seems missing, look for its collapse control before you assume the data is gone.

Frame grid and selection

Frame tiles show state and preview availability: finished frames show thumbnails, active frames show a spinner, and queued frames show a clock. Selecting a frame connects the grid to frame details, preview position, charts, and logs.

*One glance separates finished, rendering, and queued frames.*

These keys work while focus is not inside an input. Frame navigation follows valid frames in the configured step:

Selecting a frame fills the details panel on the left with its status, timing, and machine.

*The selected frame's status, total time, machine, and actions.*

Use Re-render after you correct or understand an issue. For an active task, the label can be Cancel and re-render. Re-render queues the frame again and can replace its existing output. If you repeat it without reading the logs, you can pay for the same failure twice.

Preview

The preview plays and scrubs the image sequence. You can also zoom, pan, and select layers when a frame has multiple render layers or outputs. The timeline and grid can show frames before every optimized preview is ready.

*Choose a render layer without leaving the sequence player. This example shows the Classroom Normal pass.*

*The timeline above the bar colors each frame by state, and the counter shows the playback position within the range.*

Preview is not original output

Web images are optimized for responsive review. Use Manage & Download in Blender for the full-quality image files and validate those before delivery or compositing.

Job and Scene details

The details panel separates operational job information (the Job tab) from the submitted scene configuration (the Scene tab).

The Summary card

*The Job tab: status with its action, the Summary readouts, and the collapsed Machines and Operation Times cards.*

Every Summary row is one reading with the same layout: the label, the current figure, and a lighter annotation to its right. Annotations that start with est are live projections. They keep refining as frames finish. Treat them as estimates, not commitments.

Every row folds open: click it to expand the breakdown behind the figure.

*The Cost row expanded. Each Summary row folds open the same way.*

What each fold contains:

Compute versus Elapsed is the key pair for judging parallelism: a job with 10 minutes elapsed and 60 minutes of compute ran roughly six machines wide.

The Scene tab

Scene preserves what the submission captured, organized into Job, Render, Output, and View layer sub-tabs. Use it to check the submitted settings, even after the local scene has changed.

*The Scene tab preserves the submitted configuration: name, format, engine, frames, version, and the farm options, with Duplicate job below.*

Charts and logs

The operations chart compares phase timing across frames. Per-machine GPU, VRAM, CPU, and RAM telemetry appears in the Job overview's Machines card. Use both to form a hypothesis, then confirm it against frame details and logs. Utilization alone does not prove the bottleneck.

*Each bar stacks a frame's download, render, and upload time. Select a frame to read its exact numbers on the left.*

Switch the same panel to Logs for the selected scope's render output.

*Search with match navigation, a minimum-severity filter, text sizes, and log download live in the panel header.*

The log view supports:

• XS, S, M, and L text sizes
• text search and previous/next match navigation
• severity filtering
• log download for offline review or support

Select the exact failed frame before you diagnose a frame-specific error. When the order of events matters, send a downloaded log, not a cropped screenshot.

Machines and timings

Machine information helps explain parallelism and which frames ran where. Expand the Machines card in the details panel for per-machine telemetry.

*The Machines card expanded: live utilization with Average or Per node views, the metric tiles, and each machine's frame tally.*

Reading the card:

• The Machines row counts the nodes assigned to the job, with their aggregate state (for example all active) beside it. Its fold breaks down Compute (summed machine time), Est. total, and Active now.
• The chart plots the selected metric over the recent window. Average blends all machines into one line. Per node draws each machine separately so one struggling node stands out.
• The metric tiles switch the chart between GPU (compute utilization), VRAM, CPU, and RAM, each showing its current reading and a spark of its recent history.
• The machine list shows each node with the number of frames it has completed and an activity bar. Selecting a machine opens its spec plate: what it is rendering right now (frame, operation), Last seen, Uptime, Send errors, its frame Range on this job, Time on job, and per-frame timing (Fastest, Slowest, Job average) alongside its Download, Upload, and Render only splits.

Operation Times

The Operation Times card shows where the job's machine time went. It has one row per operation (project download, render, thumbnail generation, output upload). Each row folds open into Avg per frame, Cost, and % of total, with a Total row at the bottom. It answers a different question than the chart panel: the operations chart compares phases *across frames*, while this card sums them *across the job*.

The first frame on a machine can include project download and startup work that later frames avoid. Compare similar frames, and keep these measures apart:

• wall-clock elapsed time
• aggregate machine time
• render time
• the surrounding download, scene-build, thumbnail, and upload operations

Download original output

The web app does not download full output. The job header points you to Blender instead: open Render Properties → Superluminal Render → Manage & Download, select the job, and choose Download job output.

*The header's Download chip explains the flow and marks the exact button in the add-on.*

• Output guide: Plan download, validation, and retention for original frames.
• Manage & Download: Run a resumable job-output transfer from Blender.
• Troubleshoot frames: Turn logs and exact-frame reproduction into a focused fix.