Architect Flow 400 Validation Error on BYOC AU-1 Terraform Apply

Architect & Flows
1

Why does the architect flow creation is failing with a 400 Bad Request during Terraform apply on our BYOC environment?

Background

We are migrating our IVR architecture to a fully automated CX-as-Code pipeline. The goal is to provision a standard routing flow using the genesyscloud_architect_flow resource. We are using Terraform 1.6.0 and the Genesys Cloud provider 2.5.1. The environment is AU-1 BYOC. The deployment runs via GitHub Actions using OIDC authentication. The flow JSON has been validated against the OpenAPI spec locally and passes basic schema checks.

Issue

The terraform apply command fails immediately when attempting to create the resource. The error response from the API is generic but indicates a validation failure in the flow definition body.

Error: Error creating Architect Flow: 400 Bad Request
{ "code": "invalid_request", "message": "Validation failed for field 'contactAttributes'" }

The specific HCL block causing the failure is below:

resource "genesyscloud_architect_flow" "ivr_main" {
 name = "Main IVR Flow - Terraform"
 description = "Automated IVR routing flow"
 flow_json = <<-EOT
 {
 "contactAttributes": {
 "routing": {
 "skills": [{ "id": "${genesyscloud_routing_skill.main.id}" }]
 }
 },
 "startNode": "Start",
 "nodes": [
 {
 "id": "Start",
 "name": "Start",
 "type": "Start",
 "transitions": [
 {
 "nextNode": "TransferToQueue",
 "expression": "true"
 }
 ]
 },
 {
 "id": "TransferToQueue",
 "name": "Transfer To Queue",
 "type": "TransferToQueue",
 "settings": {
 "queueId": "${genesyscloud_routing_queue.main.id}"
 }
 }
 ]
 }
 EOT
}

Troubleshooting

  1. Verified the skill ID and queue ID exist and are active in the target environment.
  2. Tested the exact same JSON payload via Postman against the /api/v2/architect/flows endpoint. It succeeds with a 200 OK.
  3. Confirmed the Terraform state file is clean and no drift exists.
  4. Checked the BYOC audit logs. No specific error details beyond the 400 status.

The discrepancy between the successful Postman test and the failing Terraform apply suggests a serialization or dependency issue within the provider, or perhaps a timing issue where the referenced resources are not yet fully propagated in the BYOC data store. Any insights into this behavior would be appreciated.