Print job scheduling conflicts

Because Report Scheduler prints jobs in order of priority, scheduling conflicts are possible. Scheduling conflicts within the reporting service occur for these reasons:

• The schedules set for individual reports may be in direct conflict with schedules higher up in the hierarchy. For example, if you schedule a report to print at 7:00 P.M., but assign it to a queue that is not going to be active until 10:00 P.M., your report does not print until at least 10:00 P.M.
• Even if there is no direct scheduling conflicts, during heavy system loading activity reports can become backlogged and does not print when expected. Used properly, Report Scheduler can keep these backlogs to a minimum.

You can take steps to resolve unforeseen and undesirable scheduling conflicts. If a print job is scheduled in an inactive queue, you can move it to an active queue. If several stored jobs are clogging your system during a certain time of day, or if a job needs to run sooner, you can reschedule those print jobs.

Occasionally, a job does not print because of an error, not because of a system backlog. If this happens, you can restart the print job.