Looks like in a recent update, the sort of the schedule time in S3 execution history treats time as a number not as a time. This example shows that it is sorting 1PM before 10AM on the same day.
Already have an account? Login
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
This appears to still be an issue.
This issue has been fixed now. You should see the logs being sorted correctly.