Running into a weird issue with the Genesys Cloud Terraform provider (v1.12.0) when trying to manage auth divisions. I’m setting up a new environment in the us-east-1 cluster and need to create a dedicated division for our custom desktop widgets. The plan looks fine, but terraform apply bombs out with a 409 Conflict.
Here is the resource block I’m using:
resource "genesyscloud_auth_division" "widget_div" {
name = "Widget-Dev-East"
description = "Division for custom agent desktop widgets"
}
The error message is:
Error: Conflict: A division with the name "Widget-Dev-East" already exists.
This is frustrating because I’ve checked the UI and the API directly. I ran a GET request to /api/v2/auth/divisions and filtered for that exact name. Nothing comes back. Not even a soft-deleted record. I tried changing the name to Widget-Dev-East-2 just to be safe, and it worked instantly. So the provider isn’t broken, but it seems to think the first name exists when it clearly doesn’t in the active list.
I’ve tried these steps:
- Hard refresh of the Terraform state file.
- Searching the API for partial matches.
- Waiting 10 minutes in case of eventual consistency delays.
- Checking if the name was used in a previous, now-destroyed state (I’m using remote state with S3, and the history is clean).
Is there a hidden cache on the platform side that Terraform is hitting? Or maybe a soft-delete tombstone that the GET endpoint doesn’t return but the POST endpoint checks against? I need to use a specific naming convention for our CI/CD pipeline, so I can’t just keep appending random suffixes. Looking for a way to force the creation or find out what’s blocking it.