Agent Scripting resource fails with 400 on nested node definition

I can’t seem to figure out why the genesyscloud_agent_script resource rejects valid JSON structure during plan apply.

Context:
Using terraform-provider-genesyscloud 1.45.0. The script contains a simple linear flow with a single Q&A node. Manual API call to POST /api/v2/agent-scripting/scripts succeeds. Terraform throws 400 Bad Request citing invalid schema on the nodes block.

Question:
Is there a known limitation in the HCL mapping for nested script nodes that requires a workaround or specific attribute ordering?