Ran into a weird issue today with our BYOC Edge deployment when attempting to push updated schedule configurations via the WFM API. We are seeing intermittent 502 Bad Gateway errors specifically when the payload includes shift swap approvals for agents located in our Chicago timezone cluster. This only happens during our weekly publish window on Tuesdays at 05:00 CST.
The Edge node logs show successful handshake with the Genesys Cloud platform, but the subsequent POST request to /api/v2/wfm/scheduling/schedules/{scheduleId} times out. We have verified network connectivity and firewall rules between the Edge node and the cloud endpoint. The issue persists even after restarting the Edge service and clearing the local cache.
Has anyone else experienced latency spikes or gateway errors when integrating WFM schedule publications with a BYOC Edge setup? We are currently running Genesys Cloud version 2024.2 and Edge version 10.5. Any insights into whether this is a known limitation with large payload sizes or a configuration mismatch would be appreciated.