imauAX2541

Manage scheduled jobs

The Scheduled Jobs tab of the Scheduler dialog shows all jobs that are scheduled to be processed or are in process. This includes scheduled jobs, jobs run manually with Run Now, and jobs that were triggered to run with an event handler.

By default, this list appears when you first open Scheduler. If you have changed the view in the dialog, you can return to it by clicking the following:

  • On the Service tab, in the Service View group, click Scheduled Jobs.

If a job has a scheduling rule with a recurring schedule, only the first scheduled run appears in the list. For example, if you have a job that is scheduled to run once a month for a year, you will not see all twelve scheduled runs in the list—you will only see the first scheduled run. After that instance has been run, the scheduling rule is re-evaluated and the next scheduled run appears in the list.

In this tab, you can:

  • Stop a scheduled run. If you do not want a scheduled instance to be run, right-click the item and select Remove from Schedule. This not only removes the scheduled instance, it also inactivates the associated scheduling rule for the job (if applicable). If you want future scheduled instances of the job to proceed, you must edit the job to re-enable the scheduling rule.

  • Terminate an in-process job. If a job is already running and you want to stop it, right-click the item and select Abort Working Job. This will immediately terminate the job regardless of what it is currently doing. Depending on the type of job and its stage in the process, this may result in side-effects, such as files remaining locked or incomplete processing. No notifications will be sent for the terminated job. Generally, this action should be reserved for situations where a job has gotten stuck or was started in error.

  • Reschedule a run. To change the scheduled start date/time of a scheduled instance, right-click the item and then select Reschedule Start Time. The Start Time field in the grid is now editable, and you can enter a new date and/or time.

  • Refresh the list. On the Service tab, in the Actions group, click Refresh. New scheduled jobs will be added to the list, and Status and Due In will be updated appropriately.

NOTE: Users with the Scheduled Jobs User security permission can only modify jobs that they placed on the schedule. Jobs scheduled by other users are visible but are grayed out and unavailable for editing. Admins can view and edit all scheduled jobs.

You can also view the job schedule and perform limited management tasks using the Scheduler area of the Web Client. For more information, see Manage the job schedule in the Web Client.

Scheduled job information

The following information appears for each scheduled job:

Item Description

ID

The system-generated ID for the job run. Each scheduled run of a job has a unique ID. Job results are listed by run ID.

Job

The name of the job.

User

The user identity that the job will be run as. If the job is a system job, the user is System.

This is typically the name of the user who placed the job on the schedule but not always (for example, when using an event handler that is set to run as the job owner instead of as the requester).

Status

Job status is either Pending (waiting to be run) or Working (currently being run).

Server

If a job is currently Working, the server running the job is listed. Otherwise, this column is blank.

Priority

The priority category for the job:

  1. Manual: The job was run manually.
  2. Event Handler: The job was run by a Scheduler event handler.
  3. Scheduled Job: The scheduled instance of the job results from an active scheduling rule.
  4. Subordinate Job: The job was generated as a subordinate job from a job currently running.

The priority category determines how jobs are evaluated for processing order, in conjunction with the job's Priority Elevation setting. Manual jobs are highest priority and subordinate jobs are lowest priority. For more information, see Process priority for scheduled jobs.

Start Time

The start time of the job. The job is eligible to run immediately if the start time is now or passed. Jobs may not be run at the start time if no Scheduler threads are currently available to run the job or if other eligible jobs have higher priority.

If the job is on the schedule due to a scheduling rule, the start time is based on the scheduling rule. If the job was manually run with Run Now or triggered by an event handler, the start time is the time the run was initiated.

Due In

The length of time until the job is due to be processed. For example, if the job is scheduled to run at noon and it is currently 11:50 AM, the job is due to be run in 10 minutes.

This column is intended to make it easy to see when a job will be run without needing to calculate it based on the start time.