Terraform apply fails with 409 Conflict on genesyscloud_auth_division

General Discussion
1

Can anyone clarify why my Terraform apply keeps throwing a 409 Conflict error when I attempt to create a new genesyscloud_auth_division? I am building a lightweight SvelteKit server route to automate environment setup, and this block is blocking the entire pipeline.

Here is the resource definition:

resource "genesyscloud_auth_division" "internal_portal" {
 name = "Internal Portal Widgets"
 description = "Division for SvelteKit status components"
}

The error response indicates a name collision, but I have verified that no division with this name exists in the Genesys Cloud UI. I suspect the API might be case-sensitive or there is a hidden default division I am missing.

  • I have manually checked the /api/v2/auth/divisions endpoint via Postman and confirmed no matching record exists.
  • I tried adding a unique suffix to the name, but the error persists with the exact same 409 status code.

Is there a specific constraint or hidden state I am missing in the Terraform provider?