We are managing a hybrid telephony environment using the Genesys Cloud Terraform provider. Everything was stable until we started seeing persistent drift on genesyscloud_routing_queue resources during terraform plan. The state file shows the queue exists, but the provider insists on recreating it or modifying attributes that haven’t changed in the UI.
I suspect this might be related to a stale state lock or a race condition with concurrent API calls, but I’m not sure. Here is the relevant block:
resource "genesyscloud_routing_queue" "support_queue" {
name = "Support Queue"
description = "Main support queue"
enabled = true
acd_skills = ["english", "tech"]
}
Running terraform apply fails with a conflict error suggesting the resource is locked. I’ve tried terraform force-unlock, but the drift persists in subsequent plans. The API response from /api/v2/routing/queues shows the correct configuration, yet Terraform sees a mismatch.
Has anyone encountered this specific state lock behavior with routing queues? Is there a way to force a refresh of the local state without destroying the resource?