Quick question about WebRTC softphone behavior when agents transition between scheduled shifts in our Chicago-based operations. We are seeing intermittent connection drops for agents using the Genesys Cloud Desktop softphone (v2023.11.0) precisely at the boundary of scheduled shift changes. The issue seems to correlate with the automatic status updates triggered by the WFM schedule publication. Agents report that their softphone status flips to ‘Offline’ or ‘Break’ unexpectedly, even though their scheduled shift has just started or extended. This disrupts predictive routing queues and causes missed interactions during peak hours. We have verified that the agent’s shift data in WFM is correct and that the schedule publish completes without errors. The problem appears specific to the softphone client’s handling of the availability state change from the WFM integration. We are using the standard WebRTC implementation without custom softphone configurations. Has anyone encountered similar WebRTC softphone disconnects or status synchronization issues during WFM-driven shift transitions, and are there specific API endpoints or client-side logs we should be examining to diagnose the state mismatch?