Stuck on a persistent Error: no matching routing queue found when attempting to reference an existing genesyscloud_routing_queue via its name in a Terraform data source block. We are trying to decouple our infrastructure state by using data "genesyscloud_routing_queue" "existing" { name = "Customer_Support_Queue" } instead of hardcoding resource IDs, but the provider consistently fails to locate the resource despite the name matching exactly in the Genesys Cloud admin console. I have verified that the genesyscloud_routing_queue resource exists and is not in a pending state, and I have even tried adding depends_on to ensure the data source runs after the initial import, but the lookup still returns an empty result set. The error trace suggests the underlying API call to /api/v2/routing/queues is returning a 200 OK but filtering out the expected result, possibly due to a mismatch in the internal ID resolution logic or a caching issue with the Terraform provider’s client. Has anyone encountered this specific behavior with the genesyscloud_routing_queue data source when using the name attribute for lookups? I am currently on provider version 1.28.0 and need a workaround to reference this queue ID dynamically in my genesyscloud_routing_skill_group configuration without resorting to manual ID injection.