Running into a 409 Conflict error when trying to create a new auth division via the Terraform provider. The setup is straightforward: we’re spinning up a new org environment and need a dedicated division for our Android app’s OAuth client.
Here’s the resource definition:
resource "genesyscloud_auth_division" "app_division" {
name = "App-Division-Prod"
description = "Division for mobile app auth"
}
The terraform plan looks clean. No changes detected except the creation. But when I run terraform apply, it bombs out immediately:
Error: API call failed
with genesyscloud_auth_division.app_division,
on main.tf line 12, in resource "genesyscloud_auth_division" "app_division":
12: resource "genesyscloud_auth_division" "app_division" {
API request failed: Post "https://api.mypurecloud.com/api/v2/auth/divisions": 409 Conflict
Response body: {"errors":["The resource already exists."]}
Thing is, the division definitely doesn’t exist. I checked the UI and ran a quick GET /api/v2/auth/divisions call with Postman. The response is empty []. No App-Division-Prod anywhere.
I’ve tried clearing the state file and importing, but there’s nothing to import. The error suggests a duplicate, but the API says it’s not there. Is the provider caching something? Or is there a race condition with the default division setup?
We’re using provider version 1.42.0. The Android app code isn’t even running yet, so no active sessions or tokens interfering. Just pure infra provisioning.
Anyone seen this ghost resource issue before?