My current config is completely failing… Attempting to automate the deployment of a conversational bot configuration using the Genesys Cloud Terraform provider version 2.1.0. The pipeline executes successfully for the bot resource creation but fails immediately when applying the associated intent mappings via genesyscloud_bot_intent_mapping. The error returned is a 400 Bad Request with the message “Invalid intent reference: Intent ID does not exist or is not accessible”. However, the intent IDs referenced in the HCL are verified active and deployed in the target environment through the CLI (genesys cloud bot:intent:list). The environment is Genesys Cloud US1. The Terraform state shows the intents exist, yet the API call during apply rejects the linkage. This breaks the CI/CD pipeline for automated bot updates. Is there a known dependency issue or delay in intent availability after creation that requires a manual wait or a specific API header to resolve? The HCL block is straightforward:
resource “genesyscloud_bot_intent_mapping” “example” {
bot_id = genesyscloud_bot.example.id
intent_id = genesyscloud_flow_intent.target.id
}
No logs in the platform indicate a permission issue. The service account has full admin rights. Seeking a workaround or confirmation if this is a provider bug.