Is it possible to suppress the 409 Conflict error when toggling an outbound campaign via the Terraform provider? The environment is Genesys Cloud v2024-05. Running terraform apply on genesyscloud_outbound_campaign fails with HTTP 409 when switching the status from ‘INACTIVE’ to ‘RUNNING’ during a deployment pipeline. The API returns a conflict because the campaign is currently in a transient state. Provider version is 2.28.1. Any workaround for idempotent state changes?
The root cause here is the campaign being in a transient state that locks the status field until background processing completes.
The Terraform provider lacks native polling logic for this specific resource, so the 409 is expected behavior. Implement a retry mechanism in your CI/CD pipeline or use a null_resource with a local-exec provisioner to wait for the state to stabilize before applying the status change.
3 Likes
The documentation actually says to implement an exponential backoff retry within the Terraform module rather than relying on external shell scripts, as this keeps the state management self-contained.
- API rate limits
- Optimistic locking
- Terraform provider configuration