We’re trying to reference an existing Genesys Cloud routing queue in our Terraform configuration to attach a new flow without recreating the queue. The queue already exists in the environment, so we’re using a data source lookup.
Here’s the snippet:
data "genesyscloud_routing_queue" "main_queue" {
name = "Support Tier 1"
}
resource "genesyscloud_routing_flow" "test_flow" {
name = "Test Flow"
// ... config ...
routing_queue_ids = [data.genesyscloud_routing_queue.main_queue.id]
}
Running terraform plan throws this error:
Error: error retrieving routing queue: 404 Not Found
The queue definitely exists. I can see it in the admin UI and I’ve verified the name matches exactly, including case. We’re using the latest version of the myntra/genesyscloud provider.
Is there a caching issue with the data source or do I need to reference the ID directly? The documentation implies name lookups should work for existing resources.
This is blocking our deployment pipeline for the New Relic integration module.