Home >

AX2541

Managing scheduled jobs

The Scheduled Jobs tab of the Scheduler dialog displays all jobs that are scheduled to be processed or are in process. This includes jobs that were manually executed, and jobs that were saved with an active scheduling rule (including system jobs).

By default, this list displays 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 execution 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 executions in the list—you will only see the first scheduled execution. Once that instance has been run, the scheduling rule is re-evaluated and the next scheduled execution appears in the list.

In this tab, you can:

• Stop a scheduled execution. 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). You will need to reactivate the scheduling rule if you want future scheduled instances of the job to proceed.

• Abort 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 abort the job regardless of what it is currently doing. Keep in mind that 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 aborted job. Generally, this action should be reserved for situations where a job has gotten "stuck" or was started in error.

• Reschedule an execution. 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 type in 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.

Once a job reaches its start time, it is eligible to be processed by Scheduler, and joins the processing queue. For more information on how Scheduler determines the order of jobs to process, see Processing priority for scheduled jobs.

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. Administrators can view and edit all scheduled jobs.

Scheduled job information

The following information displays for each scheduled job:

Item	Description
ID	The system-generated ID for the job execution. Each scheduled execution of a job has a unique ID. Job results are listed by execution ID.
Job	The job name. Each job name corresponds to either a user-defined job in the Scheduler Jobs Library, or a system-managed job name generated by an Axiom Software event handler.
User	The user identity under which the job is being run. System jobs are identified as "System."
Status	Job status is either Pending (waiting to be executed) or Working (currently being executed).
Server	If a job is currently Working, then the server executing the job is listed here. Otherwise, this column is blank.
Priority	The priority category for the job: Manual: The job was executed manually. Event Handler: The job was executed by a Scheduler event handler. Scheduled Job: The scheduled instance of the job results from an active scheduling rule. Subordinate Job: The job was generated as a subordinate job, from a currently executing job. 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.
Start Time	The time the job is scheduled to start. If the job was manually executed or generated for a system job, the start time is the time the execution was initiated.
Due In	The length of time until the job starts. For example, if the job is scheduled to run at noon and it is currently 11:50 AM, then Due In is 10 minutes.