S3 execution history is sorting as if it is a number, not appreciating time
Userlevel 5
+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
Userlevel 7
+3
Oh wow 11 months ago?
This appears to still be an issue.
ASCENDING:
DESCENDING:
This appears to still be an issue.
ASCENDING:
DESCENDING:
Userlevel 5
+3
+1 for this, I've seen it multiple times.
Userlevel 7
+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.
Thanks,
Kunal
This issue has been fixed now. You should see the logs being sorted correctly.
Thanks,
Kunal
Userlevel 7
+3
Yep it's working! Thanks! Can this idea get moved to Implemented?
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.
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.