Hey everyone, I’ve run into a really strange issue with the /v2/wfm/scheduling/availability endpoint returning HTTP 503 Service Unavailable specifically when our BYOC trunks failover to secondary carriers in the Asia/Singapore region. The primary trunk handles standard load without issue, but the moment traffic shifts, the WFM service appears to timeout or drop requests entirely. This impacts our real-time adherence reporting.
The error occurs regardless of the payload size. We are using the standard Genesys Cloud REST API v2. The environment is Genesys Cloud 2023-06 release. SIP registration remains stable on the secondary trunks, so connectivity is not the root cause, but the WFM microservice seems to be rejecting requests correlated with the failover event.
Here is the sample payload we are sending:
{
"schedule_id": "8a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d",
"date_from": "2023-10-01T00:00:00.000Z",
"date_to": "2023-10-31T23:59:59.999Z",
"user_ids": ["user-123", "user-456"]
}
Any insights on why the WFM service would become unavailable during a trunk failover event in Singapore? We need to ensure scheduling data remains accessible during carrier transitions.