Question
S3 execution history is sorting as if it is a number, not appreciating time
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.
