WFM Schedule API 409 Conflict during Terraform Apply

Genesys Cloud WFM
1

Struggling to figure out why the Genesys Cloud provider returns a 409 Conflict when trying to update WFM schedules via Terraform. The schedule exists and is active. The ID matches. But the apply fails consistently.

Environment:
Terraform v1.9.8
Provider v1.65.2
Region: Australia/Sydney

The error message is:
Error: 409 Conflict: The schedule is currently locked by another process.

This happens even when no users are editing the schedule in the UI. The genesyscloud_wfm_schedule resource block is simple. It references the schedule ID and updates the schedule_items.

Steps to reproduce:

  1. Create schedule in WFM UI. Assign to user group.
  2. Import resource into Terraform state.
  3. Modify schedule_items in HCL. Add a new shift pattern.
  4. Run terraform apply.
  5. Observe 409 Conflict error.

The API endpoint called is /api/v2/wfm/schedules. The response body contains a reason field saying LOCKED.

I checked the WFM API docs. There is no explicit lock mechanism exposed in the standard REST API for schedules. Is this a provider bug? Or is there a hidden locking state I need to clear?

Using force_unlock flag in provider config does not help. The error persists.

Any ideas on how to bypass this lock via code? Or is this a known limitation of the provider for WFM resources?