Terraform Import Failing - Queue Doesn't Attach to Skill

Trying to import an existing queue - queue-a - into Terraform, but it’s consistently failing to attach to the skill - skill-x. The import command runs clean, no errors there, but the skill association just…doesn’t stick. Feels like a state drift issue, but I’ve blown away the state file, re-authenticated, and re-run the import. Still no dice.

Here’s the HCL:

resource "genesys_cloud_queue" "imported_queue" {
 name = "queue-a"
 division_id = "1234-abcd-5678-efgh"

 lifecycle {
 ignore_changes = [
 skill_ids
 ]
 }
}

resource "genesys_cloud_skill" "imported_skill" {
 name = "skill-x"
 division_id = "1234-abcd-5678-efgh"
}

resource "genesys_cloud_queue_skill" "queue_skill" {
 queue_id = genesys_cloud_queue.imported_queue.id
 skill_id = genesys_cloud_skill.imported_skill.id
}

The API is returning a 200, which is annoying. We’re on terraform v1.6.6 and the provider version is v4.18.0. Latency to the Genesys Cloud API from Chicago is brutal today - taking like 300ms just to hit the endpoint. Think the Terraform provider might be timing out before the association propagates or something. Quick win to get this shipped, honestly.

The skill association is separate from the queue resource itself. Terraform usually struggles with these linked resources during import. It’s a common problem - we’ve seen this before in the community, actually, with queue-skill assignments. The skill needs a dedicated resource block in Terraform, referencing the queue.

Try adding this to your HCL. It might help with the import.

resource "genesys_cloud_queue_skill_assignment" "imported_skill_assignment" {
 queue_id = genesys_cloud_queue.imported_queue.id
 skill_id = "skill-x"
}

It’s similar to BYOC edge promotions - the linked items need to be explicitly defined. Sometimes Terraform’s import process doesn’t pick up these dependencies automatically. There was a post last month about a similar issue with data actions, so you’re not alone.