Stuck on a problem and need help troubleshooting a deployment failure in the WFM module.
Running terraform apply with provider version 1.45.0 against the AU1 region. The pipeline hangs on genesyscloud_wfm_schedule_group. After 3 retries, it fails with a 500 Internal Server Error.
The schedule group exists in the UI. Manual API calls to GET /api/v2/wfm/scheduling/schedule-groups/{id} return 200 OK. The issue seems isolated to the PUT request triggered by the provider during the apply phase.
Error: Error applying plan for module.wfm.genesyscloud_wfm_schedule_group.main
with module.wfm.genesyscloud_wfm_schedule_group.main, on wfm.tf line 12, in resource “genesyscloud_wfm_schedule_group” “main”:
12: resource “genesyscloud_wfm_schedule_group” “main” {Error: Post “https://api.au1.genesys.cloud/api/v2/wfm/scheduling/schedule-groups”: dial tcp 52.64.12.8:443: i/o timeout
Retrying… (Attempt 3/3)
Error: Post “https://api.au1.genesys.cloud/api/v2/wfm/scheduling/schedule-groups”: context deadline exceeded
The timeout occurs specifically when updating the effectiveDate range. No changes to the underlying schedule data.
Environment:
- GC Provider: 1.45.0
- Region: AU1
- Terraform: 1.6.0
Is this a known latency issue with the WFM scheduling API during peak hours (Sydney time 09:00-10:00 AEST)? Or is there a specific retry configuration in the provider I am missing?
Logs show the request is sent but never receives a response. Not a 429 rate limit. Just a hard timeout.