Can anyone clarify the expected behavior for messaging application provisioning when the underlying WhatsApp provider is already linked?
Running into a 409 Conflict error during terraform apply on our AU-1 BYOC instance. The provider version is v1.15.0. The error response indicates that a messaging application with the specified provider ID already exists, yet no resource is visible in the Genesys Cloud UI under Digital > Messaging.
The HCL snippet is minimal:
resource "genesyscloud_messaging_application" "whatsapp_prod" {
provider_id = var.whatsapp_provider_id
name = "WhatsApp Prod Channel"
enabled = true
}
The provider_id is valid and confirmed via genesyscloud_messaging_provider data source. A manual GET request to /api/v2/messaging/applications returns an empty array. This suggests a state drift or a backend orphaned record.
Has anyone encountered this specific 409 on AU-1 BYOC? Is there a force-delete API endpoint to clear the ghost record, or should we wait for a TTL expiration? The deployment pipeline is blocked.