Legacy Dev Forum Posts

James_Tarling | 2024-01-08 09:57:50 UTC | #1

We have found that the data retrieved from the conversation APIs for a specific conversation can be inconsistent and that we can actually lose data over time

Conversation with ID 315b9a29-bca9-421c-91d4-c0880b7de639 was first retrieved by us at 2023-11-07 13:08:04.799000 UTC using /api/v2/analytics/conversations/details/query - the response is attached as first.json.

The next request was at 2023-11-08 03:12:58.398000 UTC using /api/v2/analytics/conversations/details/jobs, attached as second.json

Missing in the second request are:

• the whole participant object with id 34725e8f-65f3-480e-a193-2df15b05d247
• a value for mediaEndpointStats from session 5e3ef610-c4be-41f1-b2a1-3c7fe82350d0, together with the nConnected metric and the first segment with type system
• the nFlow metric for session 456f4aba-a807-428e-92c3-a5815c80ff02 and the first segment with type system

We made 5 subsequent requests using /api/v2/analytics/conversations/details/jobs. The last request we made was at 2023-11-14 02:21:57.392000 UTC with /api/v2/analytics/conversations/details/jobs and the response is attached as last.json

• all metrics are now missing from sessions 5e3ef610-c4be-41f1-b2a1-3c7fe82350d0 and 456f4aba-a807-428e-92c3-a5815c80ff02
• the participant with 34725e8f-65f3-480e-a193-2df15b05d247 has reappeared in the last response

These endpoints are not behaving as expected - we would reasonably expect subsequent responses to contain the same data or be a superset of the previous responses, not to contain less data.

Please could someone from Genesys explain this behaviour?

Many thanks

system | 2024-02-07 09:58:03 UTC | #2

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

This post was migrated from the old Developer Forum.

ref: 23983