Struggling to figure out why the WebRTC softphone handshake fails with a 408 Request Timeout when the WFM module attempts to publish schedules for queues exceeding 500 agents. The environment is Genesys Cloud Release 2024.2 (US-East-1) with WFM Module Version 2024.2.1. The failure occurs specifically during the /api/v2/wfm/schedules/publish endpoint call, which triggers a real-time availability sync. Our custom Python SDK v3.4.2 logs show that the WebRTC connection drops precisely when the schedule adherence engine tries to validate agent preferences against the new shift assignments. The BYOC Edge nodes in Chicago are healthy, and latency is under 50ms, yet the softphone clients for agents in the affected queues report ‘Connection Reset by Peer’ errors. This breaks the agent self-service interface, preventing shift swaps and time-off requests from processing correctly. The issue is isolated to queues with high shift swap activity. We have verified that the firewall rules allow all necessary WebRTC ports. Is there a known limitation on concurrent WebRTC sessions during bulk schedule operations, or is this a configuration issue with the Edge node routing?