jdrummonds | 2017-06-06 23:55:30 UTC | #1
When I run a version of "Queue Metrics Interval Report" for 6/5/17 I return the results as expected.
When I run the "/api/v2/analytics/conversations/aggregates/query" I get no results (as you can see in the body below I'm hoping to separate out each queue as well).
Also note, when running the API query on other days in the past results are returned as expected from the call (so, not a permissions issue etc. and I do get a 200 success result when running the body below, just no results).
Thoughts? Thanks!
Body = { "interval": "2017-06-05T07:00:00.000Z/2017-06-06T07:00:00.000Z", "granularity": "PT30M", "groupBy": [ "queueId" ] }
anon28066628 | 2017-06-07 13:24:39 UTC | #2
First guess is a timezone issue. Your query will be run in UTC time, whereas the report has its own timezone spec. You might also check the query with the interval alone, w/o the granularity or groupBy.
The tool here can help you troubleshoot.The date picker on the tool will use your local timezone too btw.
jdrummonds | 2017-06-07 15:31:29 UTC | #3
Thanks for the reply Smith_Rj!
First guess is a timezone issue. Your query will be run in UTC time, whereas the report has its own timezone spec.
I reside in the state of Arizona which is always UTC-7 (no daylight savings time). Therefore, "interval": "2017-06-05T07:00:00.000Z/2017-06-06T07:00:00.000Z" should give me the full day of 6/5/2017 local AZ time.
You might also check the query with the interval alone, w/o the granularity or groupBy.
Just did this and did get results. Then, ran with the granularity and grouping needed and now do see the results I was expecting. So, no changes to the body above, simply copied and pasted, and returned different results from the past few days. Almost as is the the query with no aggregation freed up some data some where and it became accessible again, very strange.
Can anyone clarify the behavior above so that it is not run into again? Thanks!
anon28066628 | 2017-06-07 17:58:52 UTC | #4
Ah, I didn't see that you'd factored the -7:00 into the interval instead of using timezone, that works equally well.
It might be possible that running the query without grouping and granularity caused a refresh of some part of the data, but it would be unexpected behavior.
If you see this behavior again (no data over a "new" interval when using granularity / grouping, and the data exists after running an interval-only query), could you record the ININ-Correlation-Id response headers from the two requests and open a support ticket please? The ININ-Correlation-Id lets support look up the specific API calls when troubleshooting.
jdrummonds | 2017-06-07 18:16:35 UTC | #5
I will do that, thank you!
system | 2017-07-08 18:16:49 UTC | #6
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: 1377