For the second task I have it set to skip to the 4th task on error. If I set it to continue, it would go to third task, which would reset the variable to 0 thereby causing the 4th task to never meet the condition for sending a notification.
On a side note, I think both methodologies (keeping everything contained to a single job and using a separate job for the notification) have merits. Keeping everything contained to one job is good for those who would want a notification after every failure once the threshhold has been met. Splitting the notification out to a separate job that runs on a timer is good for those would want periodic notification, but not necessarily after every single failure.
Personally, I am good with keeping it to one job because these jobs are important enough that if they fail continuously, I want to be nagged continuously until they are fixed. But if I didn't want the spam, using a separate job to reduce the quantity of notifications would be useful.
Edited by user
2011-11-28T12:22:37Z
|
Reason: Not specified