Yeah that's one I've played with but it can only detects the run time of the currently running step.

For instance I ran it just now on one of our load jobs that has been going for almost 4 hours... It only alerts at 45 minutes and below because the current step has been running about 40 minutes. Select 60 minutes and a null return...

But of course in the Job History View you can plainly see a 4+ hour total runtime. :pinch:

There is some ninja magic out there somewhere that this reluctant DBA can't whip out to look at all the job steps completed and running for a currently active job and sum them up...