edenmitchell | 2019-08-19 23:12:53 UTC | #1
Hi there,
We have noticed lately that two of the conversation analytics API endpoints do not include some existing conversations until a significant time after the conversation has finished (30 mins - 120 mins after). We only experience this from about 8am - 11am EST and it doesn't happen every day. This morning I tracked one conversation closely and these were some observations (I will put my own timestamps in UTC to match the API):
12:30:00 Request to GET /api/v2/conversations/{conversationId} returns a normal looking conversation object with an endTime of 2019-08-19T12:19:28.669Z
Request to GET /api/v2/analytics/conversations/{conversationId}/details returns status code 404
Request to POST /api/v2/analytics/conversations/details/query with a conversation filter conversationEnd = 2019-08-19T12:18:00.000Z/2019-08-19T12:21:00.000Z returns 14 conversations but the one we're looking for is not there
Following two hours I repeated the above three calls every ten minutes for the next two hours and got the same results.
14:50:00 Request to GET /api/v2/conversations/{conversationId} is the same - good.
Request to GET /api/v2/analytics/conversations/{conversationId}/details now returns a normal looking analytics conversation object with an endTime of 2019-08-19T12:19:28.669Z
Request to POST /api/v2/analytics/conversations/details/query with the same request body as before now returns 15 conversations and the one we're looking for is there.
As I monitored this one conversation, I was also taking a brief look at other conversations and during this time period I found about 10 that appeared in the conversations endpoint but returned 404 in the analytics/conversation endpoint.
Is this expected behaviour for the analytics API to sometimes take a while to add conversations? We rely quite heavily on searching conversations that ended in the last 1-3 minutes using the /api/v2/analytics/conversations/details/query endpoint - if this is expected behaviour of the analytics API, is there another endpoint we could query with similar search functionality to the details/query one, that will include the most recently ended conversations.
Cheers
tim.smith | 2019-08-20 19:22:15 UTC | #2
Missing/delayed data cannot be investigated via the forum. Please open a case with PureCloud Care to investigate.
edenmitchell | 2019-08-21 22:40:50 UTC | #3
Thanks Tim, I opened a case with PureCloud Care and got the support I needed :slight_smile:
system | 2019-09-21 22:40:51 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: 5818