If you go to the main menu “About” -> “System info” and scroll down to “Server state properties” you should see many fields including:
- “activeTask” (What’s currently running)
- “proposedSchedule” (what should happen eventually but isn’t currently in the queue like manually added jobs or the NEXT scheduled run of a job that might currently be running)
- “schedulerQueueIds” (what’s currently in the queue to be run)
If a job runs long enough that it goes past it’s next scheduled run time, it will be added to the queue (as a “missed job”) even though it’s already currently running. This means as soon as the job finishes, it will start up again to cover the “missed” start time. That may be what happened to you.
It would likely look something like this (without the color highlighting):
activeTask : {"Item1":25,"Item2":"4"}
proposedSchedule : [{"Item1":"4","Item2":"2018-05-22T01:00:00Z"}]
schedulerQueueIds : [{"Item1":26,"Item2":"4"}]
The above shows:
- Job ID 4 is currently running (it’s #25 in the queue)
- Job ID 4 is scheduled to run again at 01:00:00Z on 2018-05-22
- the Job ID 4 scheduled for 2018-05-22T01:00Z is #26 in the queue
This isn’t what you’re seeing, but there’s also a known issue with some older versions where a database cleanup step would run (locking the database) AFTER the job reported itself as being finished.