› Management Console › User interface › Schedules › Set job priorities

Set job priorities

Schedule jobs to run in a queue upon availability of required resources, such as Desktop Automation Service, license units, and RoboServer execution slots.

To create schedules, see Schedules.

View the status of queuing in the Task view, and view the history by using the "Task messages" log in the Log view.

Priority processing

How you configure jobs determines priority processing.

  • A job scheduled with a higher priority runs before jobs of lower priorities.

  • Higher priority jobs have priority access to required resources.

  • A high-priority job queuing for several minutes is executed before another high-priority job that has just entered the queue.

  • If you select "Run Jobs Sequentially," the following applies:

    • When you create a schedule with single robots, the timeout occurs after each robot in the schedule.

    • When you create a schedule containing a group of robots, the robots run simultaneously. If the timeout occurs, all robots time out, and the schedule times out as well.

  • Each schedule has a configurable timeout, and the timeout applies to all robot jobs in a schedule.

    • If a job is not executed before the timeout is reached, the job exits the queue.

    • If you have two jobs with timeouts configured, such as 300 and 600 seconds, and they are scheduled to run at the same time, the job with the shorter timeout runs before the job with the longer timeout.

    • When schedule conflicts occur, jobs with the same priority but different timeouts are prioritized based on the time they spend in the queue. The longer a job sits in the queue, the more likely it runs before another with same priority but a longer timeout.

If you have jobs of lower priorities queuing for a long time and nearly reaching their timeout, you cannot change them to a higher priority. The lower priority jobs are dropped from the queue when execution slots are unavailable to run them.

Configure a schedule

Configure each schedule using the parameters that determine priority and timeout.

  1. Set the Jobs priority parameter to the most suitable priority level.

    The following priorities from lowest to highest are available on the Management Console:

    • Minimum

    • Low

    • Medium

    • High

    • Maximum

  2. Set the Jobs timeout parameter to determine when jobs stop queuing if slots and resources are unavailable.

Resource reservation and execution

When Management Console is ready to process a job in the queue, it performs the following sequence.

  1. Starts with the highest priority job.

  2. Determines availability of a RoboServer to run the first job.

  3. Considers license distribution and RoboServer threshold.

    See General for license and threshold parameters.

    Robots use CRE licenses only when they are sent to RoboServer. While in the queue, robots do not reserve or use a license.

  4. If a job requires a resource reservation on Desktop Automation Services machines, Management Console creates a reservation.

  5. When all the conditions are met, the job is sent to RoboServer for execution.