
Monitor the rendering list
Overview
Once submitted, a job queues in the Rendering list and renders there. This page is where you watch progress, deal with a job that went wrong, and take the results away. The web console and the desktop client show the same jobs; only the entry point differs.
Page map
| Area | What is in it |
|---|---|
| Filter row | Date range, a Scene name / Job ID search box, the Status filter |
| Top toolbar | Every action for the ticked jobs — see the button table below |
| Top right | Export, Recycle bin, Custom fields |
| Frame counters | Waiting frames, Waiting (frames per node), Completed frames, Failed frames, Stop frames, Total frames, Running nodes — for every job inside the current filter |
| Job list | Scene name, Job ID, Status, Running, Completion progress, Failed frames, Frames, Rendering expense, Additional charges, Submit time, Duration, Operate |
| Row actions | Details, More; the first action follows the status, for example Download when Done, Start when Stopped |
Completion progress shows finished frames over total frames.
Status and button availability
| Status | Colour | Meaning |
|---|---|---|
| Done | Green | Every frame is rendered |
| Waiting, Rendering, Test done and other intermediate states | Blue | The job is still moving |
| Stopped | Yellow | Stopped; frames that had not started will not advance |
| Failed | Red | The job has failed frames |
Toolbar buttons act on the ticked jobs: with nothing ticked they are grey, and once a job is ticked they open up according to its status. A job that sits in Waiting for a long time usually means the chosen machine type has no free capacity, or the account balance is short — switch to a free type under Hardware and check the balance.
Toolbar buttons
| Button | What it does | When it is available | Details |
|---|---|---|---|
| Render full job | Renders the remaining frames after the priority frames are confirmed | Job is at Test done | Test frames and full render |
| Start | Continues a job, rendering only the unfinished frames | Stopped, Waiting, Test done | — |
| Stop | Stops frames that have not started; finished frames are kept | Rendering | — |
| Clone | Copies the job with the same configuration | Most statuses | — |
| Resubmit | Re-renders failed frames, stopped frames or completed frames | Job has failed or stopped frames | — |
| Delete | Moves the job to the recycle bin; the matching job in Analysis goes too | Any status | The recycle bin note below |
| Download | Downloads the results | The job has finished frames | Download and share results |
| Hardware | Changes the machine type; the new type applies only to frames that start afterwards | Job not finished | — |
| Software | Changes the software and plugin configuration; the job is resubmitted for rendering | Job not finished | — |
| Custom list in a table | Chooses which columns the list shows | Always | — |
| Clone across platform | Copies the job to another platform | Transfer assets across platform must have finished | — |
| Transfer assets across platform | Moves the job's assets; progress shows in the asset move list on Assets | Always | — |
| Select results for download | Downloads only chosen frame ranges and sequences | 3ds Max jobs with finished frames only | Download and share results |
| Export | Exports the list; the file is collected in Export record under User center | Always | — |
| Recycle bin | Restores a deleted job | Always | The recycle bin note below |
| Custom fields | Manages custom fields for the list | Always | — |
The steps, status limits and billing effects of Start, Stop, Resubmit, Clone and Clone across platform are in Stop, start, resubmit, and clone jobs. The whole path from priority frames to a full render is in Test frames and full render.
Delete and the recycle bin: a deleted job can be restored from the recycle bin. An animation job shows as expired 20 days after completion, a still-image job after 7 days; an expired job can only be inspected, and resubmit and download are unavailable — download anything worth keeping before then.
The full flow for downloading a job, selecting results by frame range and sequence, and creating an output share link is in Download and share results.
Task detail drawer
Clicking a job row opens the drawer on the right, together with a preview panel. It has three tabs — Task detail, Graph, Output file.
Task detail lets you search a single frame or a frame range, read the frame summary, and filter failed frames. Each frame offers Download, Details and Log; when one frame looks wrong, that Log holds its render log. Graph plots frame duration. Output file lists the job's output files. The preview panel switches frames and plays the sequence, and shows the actual charge, total duration, average time and cost per frame, plus the software and plugin configuration, camera, resolution and machine type.
Desktop client
The client's top bar has four tabs — Analysis, Upload, Render, Download — and Download is where finished results collect. Two things are specific to it: automatic download, which saves you from clicking each job, and the parcel icon next to a failed job, which opens a diagnostic with the problem and a suggested fix. Downloads also go through the local Raysync transfer tool.
