Terraform 400 on Screen Recording Config via API

General Discussion
1

Could someone explain why applying genesyscloud_screen_recording fails with HTTP 400?

Environment: US-1 Prod. Provider v1.15.4. Terraform v1.6.5.

Attempting to deploy screen recording rules via GitHub Actions pipeline. The config references valid org_unit_id and user_group_id. Both exist and are accessible via CLI.

Error:

Error: POST /api/v2/screenrecording/rules: 400 Bad Request
{"errors":[{"code":"bad.request","message":"Invalid request body"}]}

HCL snippet:

resource "genesyscloud_screen_recording" "this" {
 name = "Prod-Rec-Rule"
 enabled = true
 org_unit_id = "${var.org_id}"
 
 recording_rules {
 user_group_ids = ["${var.agent_group_id}"]
 recording_type = "SESSION_AND_SCREEN"
 }
}

Debug logs show the payload matches the REST API schema. Manual creation via UI works. CLI genesyscloud screenrecording create works. Terraform provider seems to reject the recording_rules block structure.

Is there a known issue with nested blocks in v1.15.4 for this resource? Or is the recording_type enum value incorrect?