9.5.2

22 • HOW TO...
HOW TO... • 23
NET
The job that was being rendered before the priorities were changed will be
stopped as soon as the new project gets a higher priority. All its clients will
stop rendering and every frame in process will be aborted (for now). When the
new, high priority, job is nished, the clients will continue with the previous
job. Not a single frame will be lost.
As a general user (as opposed to the administrator) you can only switch priorities
within your own jobs. If you're using a rendering network together with other
colleagues, you should contact the render administrator to move your more
urgent job above the others.
You can use the arrow that points down to allocate a lower priority to a
particular job.
How to Abort Jobs
Imagine you have started to render a job but notice in the job control that you are working with
the completely wrong settings (e.g. perhaps you forgot to turn on shadows). Do you have to wait
patiently for the project to be rendered and then try again? Of course not! You can abort the current
render job.
1. Go to the Jobs page. You will see your job in the Render Queue.
2. Click on Stop in the appropriate line.
This automatically moves your job to the Inactive Jobs list. There you can modify
the job (see How to update projects) or delete it completely. As far as the server
is concerned, it has nished the task and is already working on the next job.