Struggling to figure out why the abandonment metrics in the Performance dashboard for our primary voice queue do not align with the actual flow termination events logged in Architect. The environment is Genesys Cloud EU-West, operating under Standard BYOC, with the current tenant version updated to the latest release as of this morning. We are experiencing a specific discrepancy where the Performance dashboard reports a 4.2% abandon rate for the last 24 hours, while the Architect flow logs indicate that 8.5% of sessions are terminating due to a ‘Flow Timeout’ event after the maximum wait time is exceeded in the ‘Queue for Agent’ block. The queue is configured with a predictive routing strategy and a maximum wait time of 180 seconds. The ‘Flow Timeout’ action in Architect is explicitly set to transfer the caller to a voicemail prompt, which counts as a handled interaction, not an abandon. However, the Performance dashboard continues to classify these specific interactions as abandoned, skewing our service level calculations. We have verified that the ‘Abandon’ definition in the dashboard settings includes calls that end before an agent conversation is established. The issue appears isolated to calls that trigger the flow timeout logic within the first 60 seconds of entering the queue, suggesting a potential lag in the conversation state update between the Architect engine and the performance metric aggregation service. We have checked the Conversation Detail View for several sample interactions and confirmed that the ‘Reason for End’ is listed as ‘Customer Disconnected’ rather than ‘Voicemail’, which is unexpected given the flow logic. This inconsistency is causing significant reporting errors for our SLA compliance reviews during the Europe/Paris business hours. Is there a known delay or configuration requirement to ensure that flow-managed timeouts are correctly reflected as handled interactions in the Performance dashboard metrics? We need to reconcile these figures before the end of the quarter to ensure accurate reporting to stakeholders.