Asynchronous Analytics API issue

Analytics and Reporting
1

Good day.

I have a problem downloading conversations. Using the asynchronous API https://api.{{environment}}/api/v2/analytics/conversations/details/jobs

He's not giving me back various conversations. But if I query them with the API (https://api.{{environment}}/api/v2/analytics/conversations/:conversationId/details) if it succeeds in returning the conversations.

How can I correct this? Since I am using the bulk download of conversations by the asynchronous API (I understand that it is recommended).

Thanks for your support.
Julio Segil

2

Are you clear on the differences between the two APIs?
https://developer.genesys.cloud/api/rest/v2/analytics/conversation_details_job#differences-to-conversation-detail-queries

The bulk data is not real time accessible like the details query is;

An important consideration is that the jobs-backed data is not continuously updated in real-time and so depending on when you query, you may not see up-to-the-moment data. While your job might execute and have results for you ready in seconds, the data it can search/return may not be up-to-date for on the order of hours to a full day behind real-time.

It's only "eventually consistent".

3

Hi, good morning.
If I exactly understand the behavior of each API. But what I'm trying to get is data from last month. For example: From the day 2021-10-04.

And the asynchronous API is not returning some conversations that if it returns the API conversation details.

Your support please.
Julio Segil

4

You'll probably need to provide example calls to each API that are getting different results, and may want to consider opening a support request if you're absolutely certain you're asking for the same thing but getting different results.

This clause catches a lot of people >

  • Interval : Conversation detail queries will only include conversations that started on a day (UTC) touched by the interval. Conversation detail jobs will by default include all conversations whose lifetime overlaps with the query interval. If you want the same behavior as for queries, you should set the startOfDayIntervalMatching flag in the query to true.

But you are describing the opposite of what that usually looks like so I am out of possible guesses without more specifics :slight_smile:

5

Hi, Thanks for your reply. Of course I bring you the evidence of the different responses of each API. It's a conversation from 2021-10-04

Asynchronous API:

https://api.{{environment}}/api/v2/analytics/conversations/details/jobs

{

  "conversationFilters": [

    {

      "type": "or",

      "predicates": [

        {

          "type": "dimension",

          "dimension": "conversationId",

          "operator": "matches",

          "value": "0ef4dc2a-374f-4e16-b39b-8d4b4d6a821f"

        }

      ]

    }

  ],

  "order": "asc",

  "orderBy": "conversationStart",

  "interval": "2021-10-03T05:00:00.000Z/2021-10-05T05:00:00.000Z",

  "limit": 100,

  "startOfDayIntervalMatching": true

}

Outcome:

https://api.{{environment}}/api/v2/analytics/conversations/details/jobs/c4325227-fe7e-44ec-8fa2-33e91c07f623/results?&pageSize=1000
{

    "dataAvailabilityDate": "2021-10-17T03:06:56Z",

    "conversations": []

}

API COnversation Details:

image
image1326×895 62.7 KB

Thanks for your support.
Julio Segil

6

On the filter, can you try using AND instead of OR

7

Hi Robert.

I have also tried the AND and got the same result.

Greetings.

8

Not seeing anything obvious, you probably need to open a support incident for them to investigate what's going on there.

9

Please open a case with Genesys Cloud Care to investigate the conversations returned by your queries; Customer-specific data cannot be investigated in a public setting such as the forum.

1 Like
10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.