Reporting api returning empty arrays for byoc trunk failover events

General Discussion
1

Just noticed that the /api/v2/analytics/reporting/query endpoint is returning empty arrays for trunk failover metrics in the APAC region. using Genesys Cloud Java SDK 11.5.2. the primary/secondary carrier failover logic is working fine in the UI but the analytics data shows zero events for the last 48 hours. checked the date filters and they seem correct. is there a known delay or bug with the reporting pipeline for BYOC trunks in Singapore? any help would be appreciated.

2

Have you tried swapping the standard reporting query for a custom report execution? The default analytics/reporting/query endpoint sometimes misses specific BYOC edge events if the data hasn’t fully propagated through the global pipeline. In my Zendesk-to-GC migrations, we often see similar gaps with digital channel data. The analytics/report/execute endpoint is usually more reliable for real-time troubleshooting.

Try this payload structure:

{
 "reportDefinition": {
 "name": "Trunk Failover Events",
 "dataSource": {
 "type": "reporting",
 "id": "voice.trunk.failover"
 },
 "timeFrame": {
 "startDate": "2023-10-25T00:00:00.000Z",
 "endDate": "2023-10-27T23:59:59.999Z"
 }
 }
}

Check if the voice.trunk.failover data source returns results. If it does, the issue is likely just a sync delay in the standard query cache.

3

Yep, this is a known issue… when running JMeter against platform_api endpoints. The Retry-After header is useful, but it does not tell the whole story for analytics endpoints. The real problem is often…