Terraform plan drift on genesyscloud_routing_queue despite state lock

General Discussion
1

Running terraform plan on genesyscloud_routing_queue shows constant drift on outbound_call_flow_id even though the config hasn’t changed. State lock is active and no other runs are executing. The diff suggests the API is returning a different value than what’s in the state file.

# genesyscloud_routing_queue.main will be updated in-place
~ resource "genesyscloud_routing_queue" "main" {
 ~ outbound_call_flow_id = "abc-123" -> "def-456"
 }

Checked the API directly with curl and the response matches def-456. State file clearly has abc-123. Importing the resource fixes it temporarily but drift returns on next plan. Any idea why the provider isn’t syncing correctly?

2

Docs state: “The outbound_call_flow_id must reference a valid, active call flow.” If that flow was deleted or renamed, the API returns null or a different ID, causing drift. Check the flow status in the UI first.