Looking for advice on a recurring SIP registration timeout happening right when our WFM schedules publish via the /api/v2/wfm/schedules endpoint. We are on Genesys Cloud 2024.3 in a BYOC environment with America/Chicago timezone settings. The error log shows a 504 Gateway Timeout specifically during the high-concurrency publish window, which seems to collide with our SIP trunk health checks. Has anyone seen this overlap between WFM API calls and telephony infrastructure stability?
What’s probably happening here is that platform API latency during peak WFM operations, not a SIP trunk failure. The 504 indicates the gateway timed out waiting for the WFM service to respond, which can indirectly affect concurrent telephony health checks.
Stagger your schedule publishes using exponential backoff. Avoid hitting /api/v2/wfm/schedules during high-concurrency windows to prevent resource contention. Implementing jitter in your retry logic should resolve the timeout collisions.