Quick question, has anyone seen this weird error? with the reporting API when querying Architect flow metrics in our EU-West (Paris) environment. The Performance Dashboard displays accurate abandonment rates and talk times, but the raw data retrieved via the /v2/analytics/queues/report endpoint shows significant discrepancies. Specifically, the total_abandoned field is consistently lower than the dashboard value by approximately 15% during peak hours.
The environment is Genesys Cloud EU-West. The issue persists across multiple flow versions. We are using the standard REST API with OAuth2 authentication. The dashboard updates appear immediate, while the API report generation seems to lag or aggregate incorrectly.
- Verified the time zone settings on the API request match the CET time zone used in the dashboard configuration.
- Cross-referenced the
conversation_idlogs from the API response against the real-time tracing data in the Performance Dashboard to confirm the missing calls are indeed abandoned interactions.
Has anyone encountered this specific divergence between the dashboard UI and the analytics API for Architect-driven queues? Any insights into the aggregation logic differences would be appreciated.