Anyone free to help troubleshoot this deployment failure for an IVR flow definition. The Terraform plan succeeds, but the apply step fails with a 400 Bad Request when attempting to create a specific genesyscloud_architect_flow resource. This is happening in our AU-1 BYOC environment using provider version 1.3.1. The issue seems isolated to the SetContactAttributes node configuration within the flow.
The HCL snippet for the problematic node looks like this:
resource "genesyscloud_architect_flow" "ivr_main" {
name = "Main IVR Flow"
description = "Primary customer routing flow"
flow_type = "INBOUND"
# ... other nodes ...
set_contact_attributes {
id = "set_custom_attr_01"
name = "Set Customer Tier"
contact_attributes {
key = "customer.tier"
value = "${local.tier_value}"
type = "STRING"
}
transitions {
entity_ref {
id = "next_node_id"
type = "flow"
}
}
}
}
The error returned by the API is quite generic:
Error creating Architect Flow: 400 Bad Request: Invalid flow definition. The node ‘set_custom_attr_01’ contains invalid configuration. Please check the contact attribute schema.
I have verified that the attribute key customer.tier exists in the platform data schema and is writable. The value being passed via the local variable is a simple string “PREMIUM”. No special characters. The flow ID is being generated correctly in the plan stage.
Is there a known issue with the SetContactAttributes node in the GC Terraform provider for BYOC environments? Or is this a validation error on the API side that the provider isn’t catching properly? We are using GitHub Actions for deployment, so manual intervention via the UI is not ideal. Any insights on what specific field might be triggering this 400 error would be appreciated.