Scheduler triggers that are sent on success or failure of runs

When you create or edit a schedule, you can configure a trigger that the schedule sends on success or failure of a run, and you can also configure one or more schedules to listen for these triggers.

Triggers work across products. For example, a Campaign flowchart can send a trigger that starts an eMessage mailing.

A trigger is a text string that the HCL® Marketing Software Scheduler can send when a run completes successfully or when a run fails. Each schedule can send one trigger on successful conclusion of a run, and one trigger on failure of a run. Also, each schedule can listen for one success and one failure trigger.

All schedules set to listen for a trigger receive all sent triggers, but a schedule initiates a run only if it receives the trigger for which it is listening. An unlimited number of dependencies between schedules can be created in this manner.

After you have created a trigger, it appears in a dropdown list of triggers in the scheduler user interface, which makes it easy to use again.

Trigger example

You can schedule a set of Campaign flowcharts to run at the same time by configuring them to all listen for the same trigger, which can be sent by any other schedule or by an external application using the scheduler_console_client utility. You can also use triggers to cause a set of flowcharts to run in series, one after another.

The following example illustrates how to set up a series of flowcharts to run in a specified order.

  • Flowchart 1 is scheduled with a "Flowchart 1 run complete" trigger that is sent when the run completes successfully.
  • Flowchart 2 is scheduled as follows.
    • Start when a "Flowchart 1 run complete" trigger is received.
    • Send a "Flowchart 2 complete" trigger when the run completes successfully.
  • Flowchart 3 is scheduled to start when a "Flowchart 2 run complete" trigger is received.

About start triggers

A schedule that is set up with a start trigger begins to listen for a trigger as soon as it is created, regardless of its start date. However, the trigger does not override the start date. For example, if a schedule has a start date of December 12, 2016 and on December 5, 2016 it receives its start trigger, the run does not start until December 12, 2016.