Printing priority

Report Scheduler prints current jobs, not only in order of creation or scheduled run dates, but in order of their priority. One-time jobs are prioritized over non-demand jobs, and named queues over unnamed queues. Jobs of higher priority, one-time jobs and named queues, must finish executing before jobs of lower priority are eligible to execute. Printing priority is unrelated to a specific operator or queue.

This is the printing priority from highest to lowest:

1. One-time jobs in named queues
2. One-time jobs in unnamed queues
3. Standard and stored jobs in named queues
4. Standard and stored jobs in unnamed queues

One-time jobs are given a higher priority than other jobs because of the time-sensitive nature of most one-time jobs. If a customer requests an invoice, they should receive it as soon as possible. Stored jobs are the lowest priority. For example, your accounts receivable clerks could schedule their aging reports to run in the middle of the night so they are finished by morning.

Stored reports are at the bottom of the scheduling hierarchy of the reporting service. If a report is scheduled to run on a certain date and at a certain time, but is assigned to a queue, the scheduling for the queue takes precedence over the schedule set up for the stored report. A report is not executed until its scheduled date and time have passed, but it may be executed later than its scheduled date and time depending on other priorities within the reporting service.