Noted. At first glance I'm not sure what we can do about that.
Based on the information you provided as well as some additional limited information we have on the server, one of two things happened:
1) For reasons unknown, amongst all the other correct tasks on that computer, this one task reported the time incorrectly, but otherwise ran correctly.
2) For reasons unknown, amongst all the other correct tasks on that computer, this one task failed for some reason and ran for a shorter period of time, but left no trace of this in the log.
The second possibility seems less likely, but in either case it's not at all obvious what the cause is or what we could do about it.
Thanks for bringing it to our attention.
My lucky number is 75898524288+1