S3 execution history is sorting as if it is a number, not appreciating time

  • 22 June 2017
  • 5 replies

Userlevel 5
Badge +1
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.

This topic has been closed for comments

5 replies

Userlevel 7
Badge +3
Oh wow 11 months ago?

This appears to still be an issue.



Userlevel 5
Badge +3
+1 for this, I've seen it multiple times.
Userlevel 7
Badge +3
I opened a support ticket on this.  It was accepted as a bug.  Hopefully fixed soon.
Userlevel 4
Hi Jeff,

This issue has been fixed now. You should see the logs being sorted correctly.

Userlevel 7
Badge +3
Yep it's working! Thanks!  Can this idea get moved to Implemented?