Can anyone clarify the calculation logic for the ‘Average Handle Time’ metric when viewed through the Performance Dashboard versus the raw data exported via the Interaction History API? We have observed a consistent 4-6 minute variance in our EU-FR production environment for queue ID 8921. The dashboard aggregates wrap-up time differently than expected, or perhaps it excludes specific flow tasks that the API includes. Our Architect flows utilize a complex routing strategy with multiple skill-based queues, and the reporting seems to double-count certain transitions when agents transfer calls between skills within the same interaction. This discrepancy impacts our SLA reporting significantly. We are using the standard Genesys Cloud UI version 2024.1. Is there a known configuration in the Performance Views that adjusts for this, or is this a limitation of how the dashboard engine processes multi-skill interactions? The business stakeholders require precise alignment between the visual dashboard and the auditable API data. Please advise if there is a specific metric definition we should reference or if this requires a ticket with Support to reconcile the aggregation methods.