We are running into a persistent issue while attempting to update an existing genesyscloud_auth_division resource using the Genesys Cloud Terraform provider (v1.8.12). The apply fails with a 409 Conflict error, yet the resource is clearly managed in our state file and exists in the target organization.
Here is the relevant configuration snippet:
resource "genesyscloud_auth_division" "support_division" {
name = "Support Division EU"
description = "Primary support division for European operations"
}
The error output from the console is as follows:
Error: Conflict
with genesyscloud_auth_division.support_division,
on main.tf line 12, in resource "genesyscloud_auth_division" "support_division":
12: resource "genesyscloud_auth_division" "support_division" {
Failed to create auth division: HTTP response code 409. Body: {"code":"conflict","message":"Duplicate name for resource type 'AuthDivision' and name 'Support Division EU' in org 'prod-org-id'"}
We have verified that the division name is unique within the organization. A direct GET request to /api/v2/auth/divisions confirms that no other division shares this name. We suspect the provider might be incorrectly interpreting the update logic as a creation attempt, or there is a race condition with the API validation layer.
We tried adding lifecycle { ignore_changes = [description] } but the conflict persists on the name field. Has anyone encountered this specific 409 behavior with auth divisions? We are considering a workaround where we manually destroy the resource in the console and re-import it, but that disrupts our CI/CD pipeline.
Any insights into whether this is a provider bug or an API quirk would be appreciated. We are currently blocked on a deployment.