Data Action 500 Error in Terraform Deployment with Custom JSON Payload

Stumbled on a weird bug today with the genesyscloud_data_action resource during our nightly IaC pipeline runs. The deployment succeeds locally but fails in the GitHub Actions runner targeting our production org in AP Southeast.

Background

We are migrating legacy integrations to Data Actions using Terraform. The goal is to create a custom Data Action that accepts a JSON payload and routes it to an internal webhook. We are using:

• Terraform v1.8.2
• Genesys Cloud Provider v1.32.1
• GitHub Actions (ubuntu-latest)

The HCL block is straightforward. We define the name, description, and integration_type as webhook. The payload structure is defined in the body attribute.

Issue

During terraform apply, the resource creation fails with a 500 Internal Server Error. The error message from the provider is generic:

Error: error creating Data Action: 500 Internal Server Error
Response Body: {"errors":[{"detail":"An unexpected error occurred during processing.","status":"500"}]}

If we remove the body configuration block and apply, the resource creates successfully but is empty. Adding the body back triggers the 500. We have verified the JSON syntax is valid using an external linter. The endpoint URL is correct and accessible from our CI environment.

Troubleshooting

• Checked Genesys Cloud system logs. No corresponding errors found for the specific timestamp.
• Tested the same payload via Postman against the /api/v2/analytics/data-actions endpoint directly. It works fine.
• Verified permissions. The CI service account has admin role and data_action:manage permissions.
• Tried changing the integration_type to email. Same 500 error occurs when body is present.
• Reduced the payload size to a single key-value pair. Still fails.

Is there a known issue with the provider parsing complex JSON in the body attribute? Or is this a backend validation issue specific to the AP Southeast region? Any insights would be appreciated.

The quickest way to solve this is to validate the JSON payload against the Data Action schema before deployment. AP Southeast regions sometimes enforce stricter payload size limits during initial provisioning. Check the input_schema in your Terraform config. Ensure no hidden characters are breaking the parser.