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.
Page 1 / 1
Oh wow 11 months ago?
This appears to still be an issue.
ASCENDING:
DESCENDING:
This appears to still be an issue.
ASCENDING:
DESCENDING:
+1 for this, I've seen it multiple times.
I opened a support ticket on this. It was accepted as a bug. Hopefully fixed soon.
Hi Jeff,
This issue has been fixed now. You should see the logs being sorted correctly.
Thanks,
Kunal
This issue has been fixed now. You should see the logs being sorted correctly.
Thanks,
Kunal
Yep it's working! Thanks! Can this idea get moved to Implemented?
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.