Genesyscloud_flow_script 400 Bad Request on AU-1 BYOC Terraform Apply

General Discussion
1

So I’m seeing a very odd bug with genesyscloud_flow_script provisioning on our AU-1 BYOC instance.

Context:
Automating script deployment via Terraform provider v1.15.0. The script JSON includes standard actions and variables. Manual creation via UI works fine. API token has flow:script:write scope.

Terraform apply fails with:

Error: POST /api/v2/analytics/queries?async=true 400 Bad Request
Body: {"errors":[{"code":"bad.request","message":"Invalid script structure"}]}

HCL snippet:

resource "genesyscloud_flow_script" "main" {
 name = "Auto-Script-Test"
 description = "Terraform managed"
 script_json = file("script.json")
}

The script.json validates against the schema. No typos in variable names. Environment is isolated. No other flows depend on this script yet.

Question:
Is the provider incorrectly routing script creation to the analytics query endpoint? Or is there a hidden dependency on a specific Architect flow version for script metadata? Any known workarounds for BYOC environments?