Of course the main duty of the rrServer is to send the jobs to the clients.
Each rrClient connects to the rrServer every x seconds to send its status and asks for a job to render.
The rrServer then chooses an job based on:
If you want to check the real priority of a job based on job and rrConfig settings, then you have to select the job and a client in rrControl and execute "Show Servers Send Decision" via the menu Debug.
It shows you the internal priority with multiple number values.
The rrServer checks each job every x seconds (or if you use the command "Check Job").
The main purpose of the check is to search for frames that are rendered.
If some Preview Frames are done, then the rrServer creates jpegs for the rrWebsite and rrControl.
It also creates an additional entry for the job stats image and it updates the framebar image.
There are two kinds of job errors.
Errors that happen at the rrServer and errors that happen at the rrClient.
Most of the rrServer errors are disabling the job immediately.
If there are rrClient errors, then a Client is de-assigned after 3 (default setting) Errors.
And if the job has 20 Client errors, then the whole job is disabled.
Errors are displayed at the job table as a small triangle.
See Error Analysis for error types