Trying to understand why my Terraform apply fails with a 409 Conflict when creating a new division via the genesyscloud_auth_division resource. The provider seems to think the resource already exists, but I can’t find it in the UI or via the REST API. I’ve verified the name is unique and checked the trash bin. No soft-deleted resources match.
Here is the resource definition:
resource "genesyscloud_auth_division" "test_div" {
name = "Integration-Test-Div-01"
description = "Automated division for Pact consumer tests"
}
The error output:
Error: Conflict creating Genesys Cloud division: 409 Conflict
{"code":"conflict","message":"Entity already exists"}
Environment details:
- Terraform v1.6.4
- Genesys Cloud Provider v1.52.0
- US East 1 Region
I attempted to debug by calling /api/v2/auth/divisions directly after the failure. The response returns an empty list for divisions matching that name.
Is there a race condition in the provider’s existence check? Or is there a hidden cache I need to clear? I’ve tried adding lifecycle { ignore_changes = [name] } but that masks the issue rather than solving it. Looking for a programmatic way to force the creation or identify the conflicting entity ID.