WebRTC softphone disconnects corrupting Conversation Detail View metrics

Just noticed that intermittent WebRTC softphone drops are failing to register as ‘abandoned’ in the EU-West BYOC environment, instead showing as completed with zero talk time. The flow logic handles the disconnect event correctly, yet the dashboard metrics remain inconsistent with the actual call logs.

flow_version: 2.1
web_rtc_timeout: 30s
queue_priority: 1
environment: EU-West BYOC

How can this discrepancy be resolved to ensure accurate service level reporting?