Hey folks,
Running into a weird blocker with our Terraform setup. We’re using the Genesys Cloud provider to manage our routing queues, but terraform plan is consistently showing drift on genesyscloud_routing_queue even though nothing has changed in the code.
Here’s the weird part: the state file seems locked or out of sync. I see this error when trying to refresh:
Error: Failed to lock state: Error acquiring the state lock: Post "https://api.mypurecloud.com/api/v2/integration/lock": 409 Conflict
I’ve tried running terraform force-unlock with the lock ID, but it complains that the lock ID doesn’t exist in the state. The code for the queue looks standard:
resource "genesyscloud_routing_queue" "support_queue" {
name = "Support Tier 1"
description = "General support queue"
enabled = true
out_of_office {
enabled = false
}
}
The API call to /api/v2/routing/queues returns the correct config, so Genesys Cloud side looks fine. It feels like Terraform is holding onto an old state snapshot that doesn’t match the remote state store.
Has anyone hit this 409 conflict on the lock endpoint specifically for queue resources? I’m thinking it might be a race condition with our CI pipeline running parallel plans, but I’m not sure how to debug the lock mechanism itself.