Terraform 409 Conflict on genesyscloud_auth_division

• Trying to understand why terraform apply throws a 409 Conflict for genesyscloud_auth_division despite the resource not existing in the UI.
• The state file is clean, and a manual GET to /api/v2/auth/divisions returns no matching ID.
• HCL snippet:

resource "genesyscloud_auth_division" "primary" {
name = "Primary-Div"
description = "Primary division for routing"
enabled = true
}

• Error output:

Error: 409 Conflict
Details: Division with name 'Primary-Div' already exists.

• The API call used by the provider seems to hit POST /api/v2/auth/divisions but fails due to a perceived duplicate.
• Is there a caching issue in the Genesys Cloud backend or a specific Terraform provider workaround for this race condition?