Event Triggers

The job was added to the production schedule on an unscheduled basis.

The job completed with a Completed Normally, Completed Abnormally, and Externally Defined statuses.

The job completed with a Completed Abnormally status. The job’s exit code is non-zero.

The job completed with a Completed Normally status. The job’s exit code is 0.

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.

The operator put the waiting job on hold.

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

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

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 Active.

The job started running.

The job was stopped by an operator.

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

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.

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 field set to Defer until completion in the Job Definition dialog for this to occur.

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 Load, Balanced Available 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.

The agent’s Enabled flag 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 Load, Balanced Available 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.

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.

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.

The end of the job’s time window might not be reached before its dependencies are met. This trigger is activated approximately 7 seconds before the job’s estimated start time becomes later than the end of the job’s time window.

The job is running longer than its estimated duration value. The job continues to run unless you stop it with a Job Control action that is associated with this event trigger, or unless an operator stops it. You initially set the Estimated Duration value in the Job Definition dialog when you create the job. TA adjusts the value to a historical average after each run of the job.

The job is running past the time window set for it in its job definition. The job continues to run unless it is stopped with an associated job control action, or unless it is stopped by an user.

The job might run past the time window set for it in its job definition. The job will continue to run unless it is stopped with an associated job control action, or unless it is stopped by the user. This trigger is activated at the end of the job’s time window minus the job’s estimated duration.

The job ran longer than the time specified in the Estimated Duration field in its job definition.

The job is running longer than its Maximum Duration value, as defined in its job definition. The job continues to run unless you stop it with a job control action that is associated with this event trigger, or unless it is stopped by an user.

The job ran in less time than the time specified in the Minimum Duration field in its job definition.

The operator ran a job again after it already completed. Once set, this trigger will only apply to jobs that were not already in the schedule.

The operator cancelled the job before it had a chance to run.

The operator aborted the job while it was running. The job could have taken too many resources, or some other problem could have occurred to justify the abort.

The operator launched the job, even though all of its dependencies weren’t met.

A job status of Launched means that a request to launch the job has been sent to the agent, and is pending notification from the agent that the job has started executing.

The job was added to the production schedule automatically.

The Master lost connection to the agent running the job and can not determine the job’s current status.

Rerunning the job would exceed the maximum reruns allowed.

The job completed within the specified exit code range. The exit code can denote normal or abnormal status for a job to trigger different actions.

Job completed normally (output pending) The job has completed normally but the job output is still being gathered and is not yet available.

Job completed abnormally (output pending) The job has completed abnormally but the job output is still being gathered and is not yet available.

Job externally defined (output pending) The job status was determined by an external user or program and the job output is still being gathered and is not yet available.

Using the duration value of the job, the job will not complete before a planned outage on its agent.

It is sent by a JobRun.

The JobRun is ready to start but will not have enough time to finish before an agent outage.

Using the duration value of the job, the job may not complete before a planned outage on its agent.

It is sent by a JobRun.

The JobRun has estimated its start time and determined it will not have enough time to run before the agent outage.

The job’s scheduled start time was reached before the job was ready to launch due to other dependencies.

This event is triggered when the job is in the Launched status longer than the specified maximum wait time.

Note: This event may not be triggered if the TA Master restarts or fails over while the job is in the Launched status.

The job may complete within the SLA risk window specified during job definition.

The job may not complete by the end time of the SLA risk window specified during job definition.

The job likely to complete within the SLA breach window specified during job definition.

The job may miss the SLA breach window specified during job definition.

The job likely to complete within the SLA risk window specified during job definition.

The job not likely to complete by the end time of SLA risk window specified during job definition.

The job likely to miss the SLA breach window specified during job definition.

The job will complete within or after the SLA risk window defined during job definition.

The job will not complete by the end time of SLA risk window specified during job definition.

The job will not complete within or after the SLA breach window defined during job definition.

The job is on the critical path of another job.

The job is no longer on the critical path of another job.

This event is triggered when the job status changes to Timed Out for a job missing its date and time window.

This event is triggered when the job status changes to Timed Out For Day for a job missing its time window for the day