Chaining

Espresso supports dynamic job chaining between two jobs. All chaining configuration is managed in the Job Chains portion of the admin web application.

A job can be chained to any other job. By default, chaining between two jobs will trigger when the source job either completes or fails, but any source termination state can be selected to trigger the chain. Chain configurations can be disabled and re-enabled at anytime. Chaining can also be constrained to a schedule, using a standard cron schedule.

Chaining will only trigger for a target job if the job has the state Enabled or Chain Active at the trigger time. A job that is Disabled or Ad Hoc Active will not be chained.

All chaining evaluations are stored. If chaining is triggered, the Job History view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or chaining schedule did not match the chain time, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.