Legacy Dev Forum Posts

 View Only

Sign Up

AnalyticsApi.PostConversationsDetailsQuery Paging/Return records change each time

  • 1.  AnalyticsApi.PostConversationsDetailsQuery Paging/Return records change each time

    Posted 06-05-2025 18:11

    rangerforme | 2017-03-09 23:40:11 UTC | #1

    I'm using the AnalyticsApi.PostConversationsDetailsQuery and paging through the results till my page returns a null or zero collections. I'm seeing very dramatic differences calling the same time interval. Each time I call the paging stops in a different place. I created this log for my testing as you can see its the same Interval, Page Count and Paging. Its the same code/same interval with different results. Anyone else seeing this?

    2017-01-06T00:00:00/2017-01-07T00:00:00 Results Page 1 - Count 100 Results Page 2 - Count 100 Results Page 3 - Count 100 Results Page 4 - Count 100 Results Page 5 - Count 100 Results Page 6 - Count 100 Results Page 7 - Count 100 Results Page 8 - Count 100 Results Page 9 - Count 100 Results Page 10 - Count 100 Results Page 11 - Count 100 Results Page 12 - Count 100 Results Page 13 - Count 100 Results Page 14 - Count 100 Results Page 15 - Count 100 Results Page 16 - Count 100 Results Page 17 - Count 100 Results Page 18 - Count 100 Results Page 19 - Count 100 Results Page 20 - Count 100 Results Page 21 - Count 100 Results Page 22 - Count 100 Results Page 23 - Count NULL Queued 2200 Items Conversation 2200 Items 2017-01-06T00:00:00/2017-01-07T00:00:00 Results Page 1 - Count 100 Results Page 2 - Count 100 Results Page 3 - Count 100 Results Page 4 - Count 100 Results Page 5 - Count 100 Results Page 6 - Count 100 Results Page 7 - Count 100 Results Page 8 - Count 100 Results Page 9 - Count 100 Results Page 10 - Count 100 Results Page 11 - Count 100 Results Page 12 - Count 100 Results Page 13 - Count 100 Results Page 14 - Count 100 Results Page 15 - Count 100 Results Page 16 - Count 100 Results Page 17 - Count 100 Results Page 18 - Count 100 Results Page 19 - Count 100 Results Page 20 - Count 100 Results Page 21 - Count 100 Results Page 22 - Count 100 Results Page 23 - Count 100 Results Page 24 - Count 100 Results Page 25 - Count 100 Results Page 26 - Count 100 Results Page 27 - Count 100 Results Page 28 - Count 100 Results Page 29 - Count 100 Results Page 30 - Count 100 Results Page 31 - Count 100 Results Page 32 - Count 100 Results Page 33 - Count 100 Results Page 34 - Count 100 Results Page 35 - Count 100 Results Page 36 - Count 100 Results Page 37 - Count 100 Results Page 38 - Count 100 Results Page 39 - Count 100 Results Page 40 - Count 100 Results Page 41 - Count 100 Results Page 42 - Count 100 Results Page 43 - Count 100 Results Page 44 - Count 100 Results Page 45 - Count 100 Results Page 46 - Count 100 Results Page 47 - Count 100 Results Page 48 - Count 100 Results Page 49 - Count 100 Results Page 50 - Count 100 Results Page 51 - Count 100 Results Page 52 - Count 100 Results Page 53 - Count 100 Results Page 54 - Count 100 Results Page 55 - Count 100 Results Page 56 - Count 100 Results Page 57 - Count 100 Results Page 58 - Count 100 Results Page 59 - Count 100 Results Page 60 - Count 100 Results Page 61 - Count 100 Results Page 62 - Count 100 Results Page 63 - Count 100 Results Page 64 - Count 100 Results Page 65 - Count 100 Results Page 66 - Count 100 Results Page 67 - Count 100 Results Page 68 - Count 100 Results Page 69 - Count 100 Results Page 70 - Count 100 Results Page 71 - Count 100 Results Page 72 - Count 69 Results Page 73 - Count NULL Queued 7169 Items Conversation 7169 Items 2017-01-06T00:00:00/2017-01-07T00:00:00 Results Page 1 - Count 100 Results Page 2 - Count 100 Results Page 3 - Count 100 Results Page 4 - Count 100 Results Page 5 - Count 100 Results Page 6 - Count 100 Results Page 7 - Count 100 Results Page 8 - Count 100 Results Page 9 - Count 100 Results Page 10 - Count 100 Results Page 11 - Count 100 Results Page 12 - Count 100 Results Page 13 - Count 100 Results Page 14 - Count 100 Results Page 15 - Count 100 Results Page 16 - Count 100 Results Page 17 - Count 100 Results Page 18 - Count 100 Results Page 19 - Count NULL Queued 1800 Items Conversation 1800 Items 2017-01-06T00:00:00/2017-01-07T00:00:00 Results Page 1 - Count 100 Results Page 2 - Count 100 Results Page 3 - Count 100 Results Page 4 - Count 100 Results Page 5 - Count 100 Results Page 6 - Count 100 Results Page 7 - Count 100 Results Page 8 - Count 100 Results Page 9 - Count 100 Results Page 10 - Count 100 Results Page 11 - Count 100 Results Page 12 - Count 100 Results Page 13 - Count NULL Queued 1200 Items Conversation 1200 Items


    tim.smith | 2017-03-10 00:11:07 UTC | #2

    Could you grab the correlation ID from the response header for the last two requests (results + null) of a test or two? I can check and see if there's some internal error that's being suppressed.

    In your script, whenever you encounter an empty result set, can you sleep for a few seconds and repeat the query for the same page, and do this a few times? I'm interested to see if you get empty results and then get more results on the next retry. If that happens, definitely grab the correlation IDs from the null and populated responses for the same page.


    rangerforme | 2017-03-10 17:39:09 UTC | #3

    Here is one example. I'm working on doing the sleep/retry to see what happens.

    ININ-Correlation-Id: 2f9f82a6-ba97-420e-9006-5fe8cc93a99e - Worked ININ-Correlation-Id: 6bf264bb-44ad-4b81-9c85-e225f3828185 - Null Results, should be results


    rangerforme | 2017-03-10 20:06:31 UTC | #4

    Here is an example of it failing then it retries right away after a 1 second sleep and worked.

    ININ-Correlation-Id: 42f09e68-e32e-4a23-8555-bf0be23c4070 - Worked - {"interval":"2017-01-06T00:00:00/2017-01-07T00:00:00","paging":{"pageSize":25,"pageNumber":19}}

    ININ-Correlation-Id: f00c6fc3-e332-4cb1-9601-4cdbdcc4fbc5 - Returned Null Collection - {"interval":"2017-01-06T00:00:00/2017-01-07T00:00:00","paging":{"pageSize":25,"pageNumber":20}}

    ININ-Correlation-Id: 0a42d5ec-7140-4704-9233-7930819f0319 - Retried and worked - {"interval":"2017-01-06T00:00:00/2017-01-07T00:00:00","paging":{"pageSize":25,"pageNumber":20}}


    tim.smith | 2017-03-10 20:21:26 UTC | #5

    Thanks for that info. This is a bug in the analytics service and is being tracked as AR-5088. A fix is currently in the works.


    rangerforme | 2017-04-05 19:50:18 UTC | #6

    Is the fix deployed for this? Thanks.


    tim.smith | 2017-04-06 18:18:24 UTC | #7

    Yes, as of 3/22/2017.


    system | 2017-08-28 19:32:51 UTC | #8


    This post was migrated from the old Developer Forum.

    ref: 1028