Cisco Cisco Tidal Enterprise Scheduler 6.2 User Guide

12005

Job waiting for 
operator release

Status Change

All the job’s dependencies have been 
met. This event trigger only occurs 
when you select the Require operator 
release option in its job definition. The 
job is now waiting for the operator to 
release it.

12006

Job put on hold

Job Control

The operator put the waiting job on 
hold.

12007

Job waiting on 
resource

Status Change

All the job’s dependencies have been 
met and the job is waiting for an 
execution slot to become available.

12008

Job not ready by end 
of its time window

Schedule 
Irregularity

The end of the job’s time window was 
reached before its dependencies were 
met.

12009

Job launched

Status Change

The queue manager released the job 
from its queue to an agent, and the job 
entered the Launched status. Launch is 
the status prior to the job becoming 
Launch.

12010

Job active

Status Change

The job started running.

12011

Job stopped

Job Control

The job was stopped by an operator.

12012

Error occurred while 
launching job

Status Change

The job status changed to Error 
Occurred. The job did not run.

12013

Job skipped

Schedule 
Irregularity

The job did not run because another 
occurrence of this job was already 
running. The job must have the 
concurrency option set to Skip in its 
job definition for this to occur.

12014

Job deferred

Schedule 
Irregularity/Status 
Change

Because another occurrence of this job 
was running when this job was ready 
to launch, the job is waiting for the 
previous occurrence to complete. The 
job must have the concurrency option 
set to Defer until completion in the Job 
Definition dialog box for this to occur