Scripting node validation fails with 400 Bad Request during Terraform Apply

General Discussion
1

Stuck on a deployment failure for an Agent Scripting configuration. The Terraform plan completes successfully, but the apply step fails with a 400 Bad Request when creating the scripting node.

Environment details:

  • Provider: genesys 1.3.1
  • Region: AU-1 BYOC
  • Terraform: 1.6.2
  • Resource: genesyscloud_flow

The error points to the scripting node definition. The JSON body sent to the API seems valid when checked against the schema, yet the Architect API rejects it.

node "scripting_node" {
 type = "scripting"
 key = "main_script"
 
 scripting {
 script_id = data.genesyscloud_script.main.id
 entry_point = "start"
 }
 
 transitions {
 entry = "true"
 next_node = "queue_node"
 }
}

Error log:

Error: 400 Bad Request

Details: Invalid transition configuration for node type 'scripting'.

The script exists and is published. The transition logic is standard. No complex conditions. Just a direct flow to a queue node.

Is there a known issue with scripting node transitions in the current provider version? Or is this an Architect API validation quirk?