data "genesyscloud_routing_queue" "dash_feed" { name = "Aggregator Primary" } returns a 404 on terraform plan even though the resource lives in the Manila org. The provider genesyscloud doesn’t scope the name lookup correctly when division_id parameters are omitted, so the dashboard dependency chain breaks every sync cycle. Switching to a hardcoded id defeats the IaC purpose and the docs don’t show a valid filter block for exact string matching, leaving the pipeline stuck.