System Event Triggers

The system queue’s (Master queue under which all other queues reside) limit has been set to zero, eliminating the possibility for any jobs to enter the production schedule.

A queue’s limit was set to zero. This may have been done to prevent jobs of a certain class from running. Note that a queue can be set to accept a certain class of jobs based on the queue’s filters. To refer to the queue in an alert message, use the Queue Name variable in the assigned action.

The number of jobs running in the overall system queue has reached the overall system queue limit, and no other jobs can run until a slot becomes available. Slots become available when a job running in the queue completes, or the queue’s limit is increased. When this trigger occurs, it indicates that either too many jobs are being scheduled for the capacity of the system, or the system capacity has been underestimated, and the system queue limit needs to be raised.

A queue cannot launch any more jobs until a slot becomes available in the queue. This may indicate that a certain class or type of job is overloading the system. To refer to the queue in an alert message, use the Queue Name variable in the associated action.

The number of jobs an agent is executing is equal to its job limit. The agent cannot start any more jobs until other jobs complete. To refer to the agent in an alert message, use the Agent Name variable in the assigned action. This system event can notify users when an agent is operating at capacity.

The production schedule compile has started. Compiling usually begins at midnight, when the Master is started on a new day, or when you select the Create Schedule menu item from the Operations menu. You can use this system event to notify users that a new schedule is being created.

The production schedule compile has completed. Compiling time is based on, among other factors, the number of jobs. Use this system event to alert users that a new schedule is in effect.

The Master was paused. Waiting jobs are suspended until the Master resumes operation. You can use this system event to notify users that the Master was temporarily paused, and jobs will not launch until the Master resumes.

The Master has been resumed from paused state. You can use this event to notify users that the Master has resumed launching jobs. Depending on how long the Master was paused, many jobs may have their dependencies met at once, which may cause a spike in system resource utilization.

An agent/adapter network connection was lost. To refer to the agent, use the Agent Name variable in the assigned action. You can use this event to warn users that an agent/adapter is no longer connected.

The Master has been shut down normally. You can use this system event to notify users that all waiting jobs will not run until the Master restarts.

A fault occurred on the Primary Master (such as the Master going down, or a network failure occurred) which caused scheduling to be transferred to the Backup Master. You can use this system event to warn users that the Backup Master took over the scheduling process. Any jobs that were manually updated after the last database replication update prior to the takeover will have to be re-entered. See the TA Fault Tolerance Guide for more information on Fault Tolerance.

The Primary Master has started. You can use this system event to notify users that jobs will resume being launched. Depending on how long the Master was stopped, many jobs may have their dependencies met at once, which may cause a spike in system resources.

The Master has recognized a new production day for which jobs are automatically compiled. You can use this event to trigger initializing variables used in dependencies.

The network connection to the fault monitor was lost.

The network connection to the Backup Master was lost.

The connection to the database was lost. Operator alerts and TA logging actions are not available because they access the database. However, the logging action can be used with the Windows event log.

The network connection to the remote Master was lost.

The agent/adapter connection has entered a scheduled outage window.

The agent/adapter connection suspended during a scheduled outage window has ended its outage. (Does not apply to connections that are disabled during the outage.) This event could apply to either the automatic enabling of the connection at the scheduled end of the outage or when an administrator manually enables the connection early.

This event is triggered when a lost connection to agent/adapter is restored.

This event is triggered when a lost connection to Backup Master is restored.

This event is triggered when a lost connection to Fault Monitor is restored.

This event is triggered when a lost connection to TA Database is restored.

This event is triggered when a lost connection to Remote Master is restored.

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

The job may not start by the beginning of the job start time window.

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

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

The job may not start by the end of the job start time window.

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

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

The job not started at the beginning of the job start window.

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

The job missed the job start time window.

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

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

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