So i thought it was going to complete...it did run longer than it has before but my celebration was for not when it returned this error:
"Null value is eliminated...

I have been using dbwarden for the past five years...including through an upgrade from sql2008 to sql2012r2.  A couple of weeks ago, SQL2012 service pack 4 came out and wrecked...

Forgot to add that the query to find the long running job returned this:

dbwarden_healthreportStart_execution_dateStop_execution_dateDuration_secs

dbWarden_HealthReport2014-07-01 06:05:00.0002014-07-01 06:06:10.000Not running

dbWarden_HealthReport2014-07-10 06:05:00.0002014-07-10 06:05:49.000Not running

dbWarden_HealthReport2014-08-18 06:05:00.0002014-08-18 06:07:51.000Not running

dbWarden_HealthReport2014-08-26 06:05:00.0002014-08-26 06:07:32.000Not running

dbWarden_HealthReport2014-10-06 06:05:00.0002014-10-06 07:59:00.000Not running

dbWarden_HealthReport2014-10-22 06:05:00.0002014-10-22...

thanks for the stop job command...but what if you run this query and it says you have a LONG RUNNING job:

SELECT jobs.name AS [dbwarden_healthreport]

, CONVERT(VARCHAR(23),ja.start_execution_date,121)

AS [Start_execution_date]

, ISNULL(CONVERT(VARCHAR(23),ja.stop_execution_date,121),...