cj-anthony | 2019-05-16 05:22:32 UTC | #1
Hi everyone,
I have a service that queries conversation information for conversations using the /api/v2/analytics/conversations/{conversationId}/details endpoint. Recently I have begun receiving conversations that do not include a ConversationEnd property.
Is anyone else seeing this? Is there a reason or a workaround?
tim.smith | 2019-05-16 14:46:50 UTC | #3
POST /api/v2/analytics/conversations/{conversationId}/details will return the specific conversation you request. If there is no conversationEnd property, that just means the conversation hasn't ended yet.
cj-anthony | 2019-05-17 01:47:55 UTC | #4
Thanks Tim. I'm seeing this for conversations going back 17 days. Is this usual? Is it possible that a conversation could still be open for so long.
Additionally this only started happening about 2 -3 months ago. I wondered if something had changed in the API.
tim.smith | 2019-05-20 13:29:16 UTC | #5
It's unusual, but not impossible, for conversations to be active that long. An email can be legitimately in a queue or assigned to a user for that long. Take a look at the conversation's participants and determine if it seems right or not. If it looks like it should be ended but doesn't have conversationEnd, please open a case with PureCloud Care to investigate.
system | 2019-06-20 13:29:18 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: 5164