Looking for advice on a persistent discrepancy between the Outbound Campaign performance metrics displayed in the Genesys Cloud Performance Dashboard and the actual agent activity logs within our EU-West (Paris) environment. The campaign is configured to dial a list of 5,000 contacts using a predictive dialing strategy with a target efficiency of 85%. According to the real-time dashboard, the campaign is showing a 92% connect rate, which seems unusually high given the known data quality issues in the source list. However, when reviewing the individual agent performance views and the conversation detail logs, the actual connected calls are significantly lower, closer to 70%. The dashboard also reports a queue wait time of 0 seconds for all outbound agents, which contradicts the agent feedback indicating they are waiting for available conversations. The Architect flow associated with this campaign includes a standard phone node followed by a disposition node, with no complex routing logic. The issue appears to be isolated to the dashboard aggregation layer, as the raw data exported from the conversation history API matches the lower connect rate observed in the agent logs. This discrepancy is causing significant confusion for the operations team, as they are relying on the dashboard metrics for real-time staffing decisions. We have verified that the time zone settings are correctly configured to CET, and the dashboard filters are set to the current hour. The problem persists across multiple campaigns and agents, suggesting a systemic issue with how the outbound metrics are calculated or displayed in the Performance Dashboard for the EU-West region. Any insights into why the dashboard might be inflating the connect rate or ignoring the actual agent wait times would be greatly appreciated. We need to ensure the accuracy of these metrics for compliance reporting and operational planning.