Analytics - segmentEnd sometimes null

[Malick]

Hello,

I develop a cron job that run every midnight and retrieve from PureCloud the last 24h conversations using /api/v2/analytics/conversations/details/query in order to store them in a relationnal database. The problem is "In very rare cases, I find the segmentEnd not set and and hours later I found it set. However segmentSart is always set and defined" :

Can you help me to explain this behaviour please ?
Thank you.

[Dariusz]

Hi, there is no segmentEnd property if the segment is not completed yet.

BTW: Maybe you want to use an existing tool to export analytics data to the database?
https://bitbucket.org/eccemea/purecloud-stats-dispatcher

[Malick]

Hi,
Thank you for your answers but I am aware about the informations you have provided to me. PureCloud Stats Dispatcher does not fit the need of our customer. In this case, the exportation run at midnight so all segments are obviously completed.
Do you have another explanation please ?
Thanks

Malick - CoverApps

[tim.smith]

there is no segmentEnd property if the segment is not completed yet.

This is the correct explanation. If you are seeing segments that you have verified are actually completed and the data isn't there, please raise an issue with PureCloud Support.

[Thomas_Larsen]

It is possible that you have agents in after call work.

If agents forget to wrap up the last conversation before they go home for the day, they will be in ACW untill the next day when they sign back in and wrap up the conversation. SegmentEnd will be missing on the agent segment in this case afair.

Even if they are signed out ect. the segment will still be active untill you have a wrapup.

Adding a max ACW time on the queue can fix this, just set it to a long timer.

[Malick]

OK thank you guys...