Genesyscloud_data_action deployment fails with 400 on AU-1

NICE CXone API & Integrations
1

I’ve spent hours trying to figure out why the genesyscloud_data_action resource fails during apply.

Context:
Environment: AU-1 BYOC
Provider: v1.22.0
Resource: genesyscloud_data_action

The deployment script works fine for standard flows and scripts. However, adding a data action to the state causes a 400 Bad Request. The error message is generic: Error creating Data Action: HTTP status code 400. No detailed payload returned in the terraform output.

HCL snippet:

resource "genesyscloud_data_action" "my_action" {
 name = "Test Data Action"
 description = "Test"
 state = "ACTIVE"

 definition {
 type = "inline"
 data = "{
 \"name\": \"testAction\",
 \"version\": \"1.0\",
 \"inputs\": [],
 \"outputs\": []
}" 
 }
}

The JSON definition is valid. Tested via Postman directly to the API endpoint, it returns 200 OK with the same payload. Terraform provider seems to be adding extra headers or modifying the body in a way the AU-1 region rejects.

Question:
Is there a known issue with genesyscloud_data_action on AU-1 BYOC with provider v1.22.0? Any workaround to bypass the 400 or debug the actual request body sent by the provider?