Query related to session Metrics data in Conversations API

[Dileep_kaRanki]

Hi Team,
Related to session Metrics data in Conversations API.
In the below response I'm seeing nFlowOutcome and nFlowMilestone with multiple metrics with only milliseconds difference.
Is this data still valid?

  "metrics": [
                        {
                            "emitDate": "2023-10-27T17:33:45.683Z",
                            "name": "nFlow",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:34:00.616Z",
                            "name": "nFlowOutcome",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:34:00.617Z",
                            "name": "nFlowOutcome",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:33:51.932Z",
                            "name": "nFlowMilestone",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:33:52.828Z",
                            "name": "nFlowMilestone",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:33:57.350Z",
                            "name": "nFlowMilestone",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:33:58.250Z",
                            "name": "nFlowMilestone",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:33:58.250Z",
                            "name": "oFlowMilestone",
                            "value": 4
                        },
                        {
                            "emitDate": "2023-10-27T17:34:00.608Z",
                            "name": "tIvr",
                            "value": 15223
                        },
                        {
                            "emitDate": "2023-10-27T17:34:00.616Z",
                            "name": "nFlowOutcomeFailed",
                            "value": 1
                        },
                        {
                            "emitDate": "2023-10-27T17:34:00.616Z",
                            "name": "tFlow",
                            "value": 14933
                        },
                        {
                            "emitDate": "2023-10-27T17:34:00.616Z",
                            "name": "tFlowDisconnect",
                            "value": 14933
                        },
                       
                        {
                            "emitDate": "2023-10-27T17:34:00.617Z",
                            "name": "nFlowOutcomeFailed",
                            "value": 1
                        }
                    ]```

[tim.smith]

If you believe that Genesys Cloud is producing invalid data, please open a case with Genesys Cloud Care to investigate. We do not have access to your org's data to perform this kind of investigation via the forum.

[Dileepkaranki]

This issue is occured for a indirect customer. So it is not possible for us to open a case.My query is can we expect nFlowOutcome and nFlowMilestone with multiple metrics with only milliseconds difference. I encountered this scenario first time. Im asking the possibilities

[tim.smith]

The metrics are generated based on the conversation data and they are expected to be correct. If you have reason to suspect that is not the case, you will have to find a way to open a case with Care; we do not have the necessary access to be able to help you with this.

[Eos_Rios]

Every time you pass from one flow to the next you will peg nFlow, nFlowOutcome, nFlowMilestone if there are any, and nFlowOutcomeFailed if it happens. If you have an IVR consisting of several interconnected flows that rapidly pass off between each other with no user interaction this is the expected result.

I absolutely hate these metrics because without an indicator of what flow they were associated with I've no idea how they're useful to anyone who has more than 2 flows.

[Dileepkaranki]

Thanks for the explanation ,Based on your response, i understood that datatype for emitdatetime should be datetime2 instead of datetime because we will be missing some data if we go with datetime field. I observed this scenario for 6 months data 268 records missed if i go with datetime and perform upserts