Configuration is broken for some reason…
Attempting to provision a new WhatsApp channel via genesyscloud_messaging_application on our AU-1 BYOC instance. The apply fails immediately with a 409 Conflict error. The error message indicates a duplicate resource ID or name, but verification confirms this is a fresh deployment with unique identifiers generated via terraform random_id.
The provider seems to be caching state incorrectly or the API is rejecting the POST request due to a hidden constraint in the BYOC environment regarding messaging application limits or naming conventions.
Environment details:
- Genesys Cloud Provider Version: 2.6.0
- Terraform Version: 1.7.4
- Region: AU-1 (BYOC)
- Resource:
genesyscloud_messaging_application - Error Code: 409 Conflict
HCL snippet:
resource "random_id" "wa_id" {
byte_length = 8
}
resource "genesyscloud_messaging_application" "whatsapp_prod" {
name = "WA-PROD-${random_id.wa_id.hex}"
description = "Automated WhatsApp Channel"
enabled = true
whatsapp {
phone_number_id = var.whatsapp_phone_id
business_id = var.whatsapp_business_id
}
}
Log output shows the request is sent to /api/v2/messaging/applications. The response body contains:
{"errors":[{"code":"duplicate_resource","message":"Resource with same identifier already exists"}]}
Checked the UI. No existing app matches the generated name. Checked the API directly via Postman with the same payload. Same 409 result.
Is there a specific cleanup step required before creating messaging applications in BYOC? Or is this a known issue with the 2.6.0 provider handling of unique constraints in the Australian region? Need to unblock the CI/CD pipeline. Any insights appreciated.