Cisco Cisco Tidal Enterprise Scheduler 6.2 User Guide

12015

Agent unavailable 
for job

Status Change

The agent or the network has gone 
down prior to the job running. 
Therefore, the job cannot complete on 
this agent. If the job uses an agent list, 
this event trigger occurs in different 
ways based on the agent list:

Ordered, Random, Balanced, or 
Rotation Agent List: If the job uses 
any of these lists, the event trigger 
occurs when all agents in the list are 
unavailable to run the job.

Broadcast Agent List: If the job uses a 
broadcast list, the event trigger occurs 
for each agent in the list that is 
unavailable to run the job.

12016

Agent for job 
inactive

Status Change

The agent’s Enabled option is set to 
Disabled, or Inactive. As a result, the 
job cannot launch on this agent. If the 
job uses an agent list, this event trigger 
occurs in different ways based on the 
agent list:

Ordered, Random, Balanced, or 
Rotation Agent List: If the job runs on 
any of these agent lists, the event 
trigger occurs if all agents in the agent 
list are inactive.

Broadcast Agent List: If the job runs 
on a broadcast list, the event trigger 
occurs for each agent in the agent list 
that is inactive.

12017

Job status changed

Status Change

Your job status changed. You can use 
this event trigger to catch all status 
changes for this job. The associated 
action occurs for all changes to the 
status of a job.

12018

Job might start later 
than expected

Schedule 
Irregularity

Other jobs which the job depends on 
are running behind schedule. This 
could cause your job to run later than 
expected. This event trigger occurs 
when one or all of the prerequisite jobs 
run longer than their estimated 
duration. The job might start later than 
originally forecast