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

  • 5
  • Problem
  • Updated 3 weeks ago
  • Solved
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.


Photo of Joseph Siudzinski

Joseph Siudzinski, Employee

  • 5,352 Points 5k badge 2x thumb

Posted 1 year ago

  • 5
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 25,400 Points 20k badge 2x thumb
Oh wow 11 months ago?

This appears to still be an issue.

ASCENDING:
 

DESCENDING:
Photo of Tom Gerth

Tom Gerth, Employee

  • 4,572 Points 4k badge 2x thumb
+1 for this, I've seen it multiple times.
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 25,400 Points 20k badge 2x thumb
I opened a support ticket on this.  It was accepted as a bug.  Hopefully fixed soon.
Photo of Kunal Bhat

Kunal Bhat, Employee

  • 982 Points 500 badge 2x thumb
Hi Jeff,


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


Thanks,
Kunal
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 25,400 Points 20k badge 2x thumb
Yep it's working! Thanks!  Can this idea get moved to Implemented?