So I’m seeing a very odd bug with the softphone dropping immediately after our weekly Tuesday schedule publish in Chicago.
WebSocket 1006 errors are hitting agents with active shift swaps, despite the /api/v2/wfm/schedules endpoint returning 200 OK.
The WebRTC handshake fails silently for these specific agents, while others with standard schedules connect fine.
Is there a known conflict between the Genesys Cloud WFM scheduling service and the WebRTC signaling layer for swapped shifts?