Could use a hand troubleshooting this persistent 400 error when applying genesyscloud_screen_recording_settings via the Genesys Cloud Terraform Provider. The environment is a standard multi-tenant instance. Terraform version is 1.7.5. Provider version is 1.65.0.
The HCL configuration is straightforward. No custom fields. Just enabling screen recording for all agents.
resource "genesyscloud_screen_recording_settings" "main" {
enabled = true
}
Running terraform apply results in:
Error: Error creating screen recording settings: 400 Bad Request
{
"code" : "invalid_request",
"message" : "Invalid JSON payload"
}
The provider logs show the outbound POST request to /api/v2/wf/recording/screen. The body sent is {"enabled":true}. This matches the OpenAPI specification exactly. I have verified the payload using Postman with the same API token. Postman succeeds with a 200 OK. Terraform fails consistently.
Checked the recent release notes for the provider. No breaking changes mentioned for this resource in v1.65.0. Tried downgrading to v1.64.0. Same error.
“The screen_recording_settings resource manages the global settings for screen recording in Genesys Cloud. It supports the ‘enabled’ attribute to toggle recording for all users.”
The documentation does not mention any additional required attributes. The issue seems isolated to the Terraform provider’s request handling or header formatting. The API endpoint accepts the payload manually. The provider rejects it.
Is this a known issue? Any workarounds? Maybe a temporary disable/enable cycle via CLI? The deployment pipeline is blocked. Cannot proceed with the IaC promotion to production. The error is reproducible on every apply attempt. State file is clean. No drift detected.
Appreciate any insights. This is the third resource this week failing with 400 despite valid payloads. Feels like a regression in the provider client library. Willing to debug further if someone can point to the relevant source code or issue tracker link.