Genesyscloud_auth_division 409 Conflict on apply

General Discussion
1

Hitting a 409 Conflict every time I run terraform apply on our auth divisions. The plan looks clean, but the apply step fails immediately.

resource “genesyscloud_auth_division” “main” {
name = “Support Division”
description = “Primary support queue division”
}

Error: Error creating division: 409 Conflict

We’re in the EU region. The division name is unique and doesn’t exist in the UI. Tried deleting the state file and re-importing, same result. The API docs don’t list a specific conflict reason for this endpoint like they do for queues. Anyone seen this?

2

The 409 isn’t a drift issue. It’s a uniqueness constraint violation. ignore_changes won’t stop the API from rejecting a duplicate name if you’re swapping it. Try fetching the division ID first and referencing that instead of letting Terraform guess.

data "genesyscloud_auth_division" "main" {
 name = "Support Division"
}

resource "genesyscloud_auth_division" "main" {
 name = data.genesyscloud_auth_division.main.name
 description = "Primary support queue division"
}

Check the response headers too. Sometimes the EU region has a slight latency spike that causes the initial create to hang, then the retry hits the conflict. If the division actually exists in the backend but isn’t visible in the UI yet, you’re hitting a race condition. Force a refresh on the state file before applying.