We’re moving our US/Eastern compliance routing setup into Terraform and the genesyscloud_routing_queue resource keeps dropping the skill assignments during apply. The queue creates fine on first run but skill_ids array gets ignored or throws validation error on second cycle. I’ve checked provider docs and syntax looks right but state file keeps showing empty list after initial apply. The routing rules depend on these skills for inbound flow so we can’t leave them out. Here is the block we are using. It works for basic queue properties but skills section seems to break the plan. The error message says something about nested attributes not matching schema and suggests using dynamic block instead. We need this to stick so compliance dashboards can pull right agent groups. Any idea why skill mapping gets wiped on second apply cycle? Provider version is 1.28.0 and we’re running terraform 1.6. The apply output shows queue id but skips skill assignment step entirely. The plan shows no changes after first run but UI shows zero skills attached. The state file looks correct locally and we’ve tried destroying and recreating the resource twice already.
resource "genesyscloud_routing_queue" "compliance_east" {
name = "US-Eastern-Compliance-Routing"
description = "Queue for regulatory call handling"
enabled = true
skill_ids = ["a1b2c3d4-e5f6-7890-abcd-ef1234567890", "x9y8z7w6-v5u4-3210-zyxw-vu9876543210"]
wrap_up_timeout = "PT30S"
member_flow = "LONGEST_AVAILABLE_AGENT"
overflow_flow = "QUEUE_EMPTY"
}