This feature has been introduced in version 22.4
Introduction
The different steps from the Workflows are performed as a series of worker daemon jobs which this screen in the Monitoring reports.
Service
...
Statuses
The worker daemon jobs can have the following statuses
...
Status
...
Meaning
...
Color
...
waiting
...
Job has yet to be picked up
...
| Status | ||
|---|---|---|
|
...
processing
...
A worker daemon is currently processing the job
...
| Status | ||||
|---|---|---|---|---|
|
...
accepted
...
The job was completed and executed as expected
...
| Status | ||||
|---|---|---|---|---|
|
...
rejected
...
The job was completed but the execution followed not the standard flow. For example the job MD5_CHECK will finish with status accepted if the MD5 was the same as the expected value; it will finish with status rejected if the MD5 value was wrong.
...
| Status | ||||
|---|---|---|---|---|
|
...
failed
...
An unexpected issue occurred, for example, a connection timeout with the destination storage
The job can be restarted by pressing the play icon next to the status
error
...
| Status | ||||
|---|---|---|---|---|
|
Priority
Worker daemon jobs have a priority which is calculated according to the rule described in Worker daemon fairness
Jobs with a higher value of priority are executed first, this is the opposite of priority Transcoding Monitoring where jobs with a lower value of priority are executed first
Screens
...
Screen
...
Description
...
Queues
...
Overview of recent jobs
...
Jobs
...
Complete overview of all worker daemons jobs
Completed or rejected worker daemon jobs are deleted after 30 days
...
Failed
...
Same as jobs but restricted to status failed
...
Statistics
...
Aggregate summary of the jobs grouped by task type
This view has a heavy performance impact on the database when rendering it
...
Server Logs / Logging
...
See Worker Deamon for details.