Hmmm...
My gut feeling is, there's a mismatch between your failed_jobs table, and sysjobhistory somewhere...
Have you gone back to basics to check?
Have you checked in sysjobhistory to see if this job is showing run_status <> 1, then checked in your failed_jobs_log to see if it's in there anyways?
Another thought. Maybe the job is running (run_status 4) when your "find jobs that errored" job runs, so it mistakenly is being inserted into failed_jobs_log and reported?
Maybe, if you can, change this:
T1.run_status != 1
to this:
T1.run_status = 0
and see what happens.