Gatesi1 | 2018-07-26 14:23:27 UTC | #1
We are using /api/v2/analytics/conversations/aggregates/query to request queue information.
{ "interval": "2018-07-25T23:00:00.000Z/2018-07-26T23:00:00.000Z", "granularity": "P1D", "groupBy": [ "queueId" ], "views": [] }
We are using this data to displayed queue volumes to staff on internal wallboards.
We are noticing that the metric "nOffered" value fluctuates on different queues making the count change dramatically between calls. Calls are made to the API approx every 4-5 seconds.
We are seeing values in counts come back at 32 for 50 calls to the API we make then the 51 st call to the API we will then get count a lot lower at around 2.
An example might be the following returned "metric": "nOffered", "stats": { "count": 32
then something like. A moment later. Then with the next call data back to original figures "metric": "nOffered", "stats": { "count": 2
This is making it very difficult for staff to trust the call volumes being presented to them.
What could possibly be making this happen?
Jason_Mathison | 2018-07-26 14:31:41 UTC | #2
The developer forum isn't really the right place to troubleshoot a misbehaving API. Please contact the Customer Care organization in order to resolve this issue.
Matt_Calton | 2018-08-10 13:15:28 UTC | #3
It may be as we have found members really helpful and where support do not appear to be able to assist to date....just an observation Jason
system | 2018-09-10 13:15:29 UTC | #4
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: 3259