Ben_Carroll | 2018-01-25 16:00:20 UTC | #1
{ "interval": "2018-01-24T05:00:00.000Z/2018-01-25T05:00:00.000Z", "order": "asc", "orderBy": "conversationStart", "paging": { "pageSize": 100, "pageNumber": 139 } }
Running this query for yesterday, 01-24-2018, I know that I have ~52900 conversations for the day. PageNumber 138 works fine and 140 also works fine. PageNumber 139, however, breaks, returning this response:
{"status":500,"code":"internal.server.error","message":"The requested operation failed with status 500","contextId":"352ca569-686a-4248-9f8e-e50d10e34950","details":[],"errors":[]}
This error is repeatable. What could be causing this and how do I fix it?
tim.smith | 2018-01-25 16:18:51 UTC | #2
Please report this via PureCloud Support. Back-end service errors (5xx responses) cannot be investigated via the forum.
anon28066628 | 2018-01-25 16:23:11 UTC | #3
Hi Ben, 500 errors must go to Support as Tim noted.
On a different note though - paging 100+ pages deep into the Conversation Detail query isn't advised. The query performance degrades quickly as you page deeper into the results. It's better to use shorter intervals and combine the results on the client-side.
Ben_Carroll | 2018-01-25 18:57:19 UTC | #4
After breaking the query out into 15 minute chunks, I'm not receiving the same error on this query. Page 12 breaks. I'll submit this as a support ticket, thanks for the info.
{ "interval": "2018-01-24T14:30:00.0000000Z/2018-01-24T14:45:00.0000000Z", "order": "asc", "orderBy": "conversationStart", "paging": { "pageSize": 100, "pageNumber": 12 } }
system | 2018-02-25 19:08:46 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: 2409