Outbound campaign api 409 conflict during terraform apply

stuck on outbound campaign deployment. terraform plan looks fine but apply fails hard.

provider version 1.45.2
terraform 1.7.0
gc us-east-1

resource “genesyscloud_outbound_campaign” “main” {
name = “campaign-test”
campaign_type = “predictive”
// … other config
}

error: Error: 409 Conflict: The campaign name ‘campaign-test’ is already in use.

checked the ui. no campaign with that name exists. checked api directly via postman. same name works fine if i create it manually. seems like terraform provider is checking against a cached state or maybe there is a soft delete issue.

tried destroying and recreating. still fails. tried adding a unique suffix. works then. but i need deterministic names for our env promotion logic.

is this a known issue with the provider or am i missing a lifecycle ignore change block? need to automate this without manual intervention. timezone syd but api logs show us-east timestamps. confusing.

Have you tried checking for a campaign in the ‘archived’ state? Terraform often conflicts with soft-deleted resources that still hold the name reservation.

Resource State Visibility Terraform Impact
Active UI/API Block creation
Archived Hidden UI Block creation