Skip to main content

Run events on job outcomes

In briefAn event runs a command in response to what a job does — a status it reaches, the termination description it ends with, an expression that is true when it finishes, or, on a legacy LSAM job, a value its agent reports while it runs. You add events per job, on the job editor's Events tab, and build the command from the event type's own fields.

Notes
  • Job Status events are checked on every status change, so they can fire mid-run; Exit Description and Completion Expression events only when the job ends. Exit Description compares against the termination description rather than the exit code.
  • An LSAM Feedback event fires each time a matching value appears or changes, while the job is still running, and [[$TRIGGER MESSAGE]] carries that value.
  • Property tokens in the command are filled in as the event fires; one that cannot be resolved stays as written, and the event still fires. The exception is the property name of a $PROPERTY:ADD: if a token in it does not resolve, the event is refused and nothing is added.
Watch out
  • A Completion Expression event fires only on True. An expression that cannot be evaluated skips the event, and it is not retried.
  • Removing a frequency the job's events are scoped to refuses the save until you fix the scope.