Is this true, will a job keep running outside of it's scheduled window? Could I be seeing such odd history because the last time the job was executed was back in January and it's been running constantly since? This doesn't really answer my first question about the next run column but I am seeing several jobs that have way back start dates, little to no run history, and next run dates that have already passed long ago. There is no break statement, so this makes me think the job is constantly going, even after the times between 12:00AM and 3:59AM when it's not scheduled. However the criteria is WHILE 1 = 1 for the loop, and the next line down after the SP is a wait for delay of 20 minutes, then the end of the loop.

The job runs a while loop with a SP that takes parameters. The last execute time is all the way back in January. It runs once every 24 hours between 4AM and 11:59PM. To simplify I'll focus on this one job that's currently executing. I don't get how this next run time is calculated and was wondering if someone did.

However a job is running right now and set to run every day, however the next run column says which passed months ago. I see a few jobs that only have a few rows of history, they are only failures and nothing recent. This somewhat relates to the no history issue.