Actions and Alerts

Tidal Automation (TA) can respond automatically to unusual situations that may arise while running a production schedule. Users can create predefined responses called actions. There are various types of actions ranging from sending an alert to the TA client to running a specific job when a designated condition occurs.

Certain job or system conditions have been designated by TA as “event triggers.” The occurrence of these conditions can be used to initiate or trigger a job and an action a user has defined.

By linking an event trigger to an action or a job, an automatic response called an event is created. When this event is associated with a condition that affects an individual job or all jobs in general, this defined response is known as a job event. If the event is associated with a condition that affects the entire system and not just jobs, this defined response is known as a system event.

Job and Action + Event Trigger = Event

Jobs, job events and actions are constructed in dialogs using a three-tier hierarchy. Each job can have any number of job events associated with it, and in turn, each job event can have any number of actions associated with it. A job triggers a job event only when its exception condition becomes true, which then triggers all of its associated actions.

Jobs, job events and actions can all be created separately and linked at any time. The job-job event-action hierarchy can be linked from the Job Event Definition dialog and from the Job Definition or Job Group Definition dialog. In the Job Event Definition dialog, you can assign multiple jobs and actions to a single job event. In the Job Definition or Job Group Definition dialog, you can assign multiple job events to the job or job group, but you cannot assign actions to job events.