JobChainingJobListener Class

public class JobChainingJobListener : JobListenerSupport

The JobChainingJobListener type exposes the following members.

	Name	Description
	JobChainingJobListener	Construct an instance with the given name.

	Name	Description
	Name	(Overrides JobListenerSupportName.)

	Name	Description
	AddJobChainLink	Add a chain mapping - when the Job identified by the first key completes the job identified by the second key will be triggered.
	Equals	Determines whether the specified object is equal to the current object. (Inherited from Object.)
	Finalize	Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)
	GetHashCode	Serves as the default hash function. (Inherited from Object.)
	GetType	Gets the Type of the current instance. (Inherited from Object.)
	JobExecutionVetoed	Called by the IScheduler when a IJobDetail was about to be executed (an associated ITrigger has occurred), but a ITriggerListener vetoed it's execution. (Inherited from JobListenerSupport.)
	JobToBeExecuted	Called by the IScheduler when a IJobDetail is about to be executed (an associated ITrigger has occurred). This method will not be invoked if the execution of the Job was vetoed by a ITriggerListener. (Inherited from JobListenerSupport.)
	JobWasExecuted	(Overrides JobListenerSupportJobWasExecuted(IJobExecutionContext, JobExecutionException, CancellationToken).)
	MemberwiseClone	Creates a shallow copy of the current Object. (Inherited from Object.)
	ToString	Returns a string that represents the current object. (Inherited from Object.)

Generally an instance of this listener would be registered as a global job listener, rather than being registered directly to a given job.

If for some reason there is a failure creating the trigger for the follow-up job (which would generally only be caused by a rare serious failure in the system, or the non-existence of the follow-up job), an error message is logged, but no other action is taken. If you need more rigorous handling of the error, consider scheduling the triggering of the flow-up job within your job itself.

Reference