Instance States

The Job is awaiting execution. Possible sub-states are:

WaitingQueueBusy – The Queue is not available for Job execution at this time. The Queue may not be started and/or it has reached its maximum Job execution limit. It could also be offline, for known (maintenance period) or unknown reasons.

WaitingConstraint – Waiting on one or more constraints (dependencies) to complete. The number of times the constraint has been checked thus are displayed in parenthesis.

WaitingDateTime – Waiting for date/time to begin execution (Deferred Trigger).

WaitingActiveInstances – Waiting for the active Job instance to complete (Job tolerates only one active instance) OR waiting for the limit of multiple active instances to complete.

WaitingRestart – A disconnect occurred between the Job Scheduler and Execution Agent - and the Jobwas not marked as Restart with Failover OR a Job failure was set to restart after “n” seconds.

WaitingExecutionAgent – A Job with Restart on Reboot is waiting for the Execution Agent/machine to become available.

The Job has been delayed in starting. This could be due to waiting for a constraint to be met, or the Queue is offline or busy. What is most important is the Job has been triggered, but it has not been moved to an Agent system to run yet.

The Job is beginning the execution phase. Variables are being evaluated. The Scheduler is beginning to communicate with the Agent that will run the Job. This phase happens after a trigger, but before the Executing phase.

The Job is being dispatched to an Execution Agent.

The Job is currently executing. Possible sub-states are:

Executing – The main Job step is executing (applicable to Process Jobs only), where process Jobs include a required "main" step (i.e. the File name property) and optional pre and post steps. The Process Job steps should not be confused with Jobs Library Job steps.

ExecutingPreStep – Pre Job step is executing (applicable to Process Jobs only).

ExecutingPostStep – Post Job step is executing (applicable to Process Jobs only).

Paused – Job is paused on execution machine.

The Job has completed processing. Possible sub-states are:

Succeeded – Job completed successfully.

Failed – Job completed in failure.

Aborted – Job was aborted.

Lost - Job status was lost.  This is typically a rare event, and generally occurs if the Execution Agent running the Job disconnects from the Job Scheduler, and when the reconnect occurs, the Agent is unable to communicate to the Scheduler what happened to the Job (sometimes it can report back an accurate status, sometimes it can not - and when it can not, the status is lost). Note: While the Scheduler attempts to reconnect to the Agent, you may see an interim instance status of Orphaned.