I’ve been wrestling with the Genesys Cloud Terraform provider for the last two days. We’re trying to adopt a code-first approach for our queue configurations, but the initial import phase is a nightmare. The goal is simple: reference existing queues by name to attach new skill groups without hardcoding IDs that change in our dev environment. I’m using the genesyscloud_routing_queue data source to look up the resource. The docs say passing the name attribute should return the existing queue object, but it keeps timing out or returning an empty result.
Here’s the snippet I’m using:
data "genesyscloud_routing_queue" "support_tier1" {
name = "Support Tier 1"
}
resource "genesyscloud_routing_skill_group" "sg_1" {
name = "SG Tier 1"
// ...
}
When I run terraform plan, it hangs for about 30 seconds and then throws this error:
Error: timeout while waiting for state to become 'available' (last state: 'pending', timeout: 2m0s)
I’ve verified the queue exists in the UI. The name matches exactly. I’ve tried adding depends_on blocks, but that doesn’t help since the data source shouldn’t depend on other resources. It feels like the provider’s search logic is broken or there’s a caching issue with the underlying API call. Is there a specific attribute I need to set to force a fresh lookup? Or is this a known limitation when dealing with high-volume orgs? I’ve checked the GitHub issues but nothing recent matches this exact behavior. The standard REST API works fine for fetching this data via Postman, so it’s definitely the Terraform provider. What am I missing here?