Error: No matching data source found for name “Priority_Queue_London”. The state file refuses to populate the ID when the genesyscloud_routing_queue data source runs during terraform plan. Step one: we pass the exact queue name into the data source block, expecting it to resolve via the underlying GET /api/v2/routing/queues call. The documentation says the name filter should match exactly, but the provider seems to be stripping trailing underscores or ignoring case sensitivity in the background query. Step two: we added a depends_on clause pointing to a separate user creation module, hoping the queue would exist by the time the data source evaluates. That didn’t help. The execution log shows a 404 coming back from the platform API wrapper instead of a 200 with a populated list.
data "genesyscloud_routing_queue" "priority" {
name = "Priority_Queue_London"
}
resource "genesyscloud_routing_skill_group" "main" {
name = "SkillGroup_A"
queue_ids = [data.genesyscloud_routing_queue.priority.id]
}
We’re running v1.54.2 of the provider. The Studio flow already references this queue by its system-generated ID, so it’s definitely live in the org. We tried switching to a search_query parameter instead of a strict name match, which actually returned multiple results and broke the interpolation. The platform API normally handles fuzzy matching on queue names when you hit the REST endpoint directly with a ?name= query string, but the Terraform provider appears to enforce a strict equality check before making the call. We’ve verified the capitalization matches the UI exactly. The state file just keeps throwing that 404 mismatch error on every refresh cycle. We’re stuck on the interpolation step.