michael | 2018-09-17 22:03:53 UTC | #1
I'm pulling in some conversation Objects, and a lot of them seemingly have an invalidly formatted date in the endTime field, two examples are:
2018-09-11T09:20:77.728Z 2018-09-11T12:78:21.613Z
Is this a known bug?
tim.smith | 2018-09-17 22:11:12 UTC | #2
Did you try updating your computer to include the new 100 minute timestamp patch? ...just kidding. That doesn't look right at all. Please open a case with PureCloud Care to report the issue. They'll need to know the conversation ID where you're seeing these incorrect values and what API you're using to retrieve it. A correlation ID from the response would also help.
michael | 2018-09-17 22:23:35 UTC | #3
:hearnoevil: haha, nice fast reply! Thanks :)
anon28066628 | 2018-09-18 13:33:31 UTC | #4
I don't immediately see a problem with the forma....
system | 2018-10-19 13:33:32 UTC | #5
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 3571