Responses allow you to customize the flow of execution through an adTempus job, or to link jobs together.
While it is executing a job, adTempus fires "events" at certain key points. For example, an event is fired at the beginning of the job; another is fired at the end of the job. If the job completes successfully a "success" event is fired. If the job fails, a "failure" event is fired.
If you want adTempus to take action based on one of these events, you associate a Response with that event. The Response defines the actions that adTempus should take in response to the event. See an example.
Each response can be triggered by any number of events, and can execute any number of actions.
The events that are available vary based on whether you are creating responses for a job or a step, and based on the kind of task a step executes. For a complete list of events for a job or task, see the help topic for the Responses property page for the job or task.
Responses are evaluated in the order that they appear in the Responses list for the job or step. Within a response, actions are executed in the order that they appear in the Actions list.
Actions are executes synchronously. That is, each action must finish before the next action starts. Each Response's actions must complete before the next Response is evaluated. And all responses must be evaluated before job execution proceeds to the next step. This is important to keep in mind when you are using Job Control actions or Script actions; see the topics for those actions for more information.