Deploying genesyscloud_messaging_provider via Terraform v1.13.0 fails with HTTP 409 Conflict. Error: “Resource already exists with different configuration.” The provider name matches existing UI config, but API response shows mismatched webhook_url hash. Manual UI updates don’t resolve the drift. CLI shows correct values. Is this a known hashing bug in the provider? See Messaging Provider Docs.
it depends, but generally terraform state drift causes this 409. check if the webhook url hash changed silently. force refresh with terraform refresh or import the existing resource. also verify no background processes are updating the config during deployment. load testing usually exposes these race conditions quickly.
The documentation actually says webhook URLs must be normalized before hashing to avoid false conflicts. Ensure trailing slashes are removed in your HCL. If the state still drifts, try importing the existing resource to sync the hash. This usually resolves the 409 without manual UI edits.
| Component | Requirement |
|---|---|
| Webhook URL | No trailing slash |
| Terraform | Import existing resource |
| Hash | Recalculate after normalization |