When creating a schedule, you schedule jobs to run in a queue upon availability of required resources, such as Desktop Automation Service, license units, or RoboServer execution slots.

During the schedule creation, set the Jobs priority parameter to the most suitable priority level: Minimum, Low, Medium, High, or Maximum. Jobs from schedules that have a higher priority are provided access to the required resources and are executed sooner than those having a lower priority. Note that jobs with a certain priority that have been queuing for some time will be executed sooner than the newer jobs with the same priority. For example, a high priority job that has been queuing for several minutes will be executed (provided access to the needed resource) sooner than another high priority job that has just entered the queue.

Also, you need to set the Jobs timeout parameter to determine when the schedule jobs are to stop queuing. If a schedule job has not been given access to the required resource and executed by the time the timeout is reached, the job stops queuing. The timeout applies to all robot jobs in the schedule.

• When a schedule with single robots is created and "Run Jobs Sequentially" is selected, the timeout occurs after each robot in the schedule.
• When a schedule with a group of robots is created, the robots always run simultaneously, even if "Run Job Sequentially" is selected. So when the timeout occurs, it causes all robots to time out, and the schedule times out as well.

The two parameters apply to all robot jobs in the schedule.

You can observe the status and history of queuing tasks in the Task view and using the Task messages log in the Log view.