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

  • 5
  • Problem
  • Updated 1 month ago
  • In Progress
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

  • 4,818 Points 4k badge 2x thumb

Posted 12 months ago

  • 5
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 23,846 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, Official Rep

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

Jeff Kirkpatrick, Champion

  • 23,846 Points 20k badge 2x thumb
I opened a support ticket on this.  It was accepted as a bug.  Hopefully fixed soon.