Error creating ai bot: 409 Conflict.
Terraform plan shows no changes but apply fails. Provider 1.15.2. Region AU1.
The bot exists but the deployment state is stale. Manual UI update works. How to force state refresh or bypass the conflict check in the HCL resource?
The problem here is Terraform state drift, not a genuine API conflict. The provider sees no changes because local state matches the last known remote state, but the server-side deployment metadata has diverged.
Run terraform refresh to sync the state file with the actual Genesys Cloud instance. This updates the local cache without modifying infrastructure. After the refresh, a subsequent apply should proceed cleanly.
| Requirement | Value |
|---|---|
| Action | terraform refresh |
| Target | genesyscloud_ai_bot |
| Follow-up | terraform apply |
Avoid bypassing the conflict check via HCL hacks. State consistency is critical for audit trails, especially in regulated regions like AU1. Forcing a bypass can create orphaned resources that break chain-of-custody logs for recording exports and digital channel metadata.