No idea why this is happening, the genesyscloud_screenrecording resource fails during the apply phase. The pipeline is designed to enable screen recording for a specific user group via the cx as code workflow.
Environment details:
- Provider:
genesyscloudv1.68.4 - Region:
au-1 - Terraform:
v1.6.4 - OS:
Linux (GitHub Actions ubuntu-latest)
The HCL configuration appears correct and passes terraform validate without issues. The goal is to set the screen recording status to enabled for a specific user_id or group context. However, the API returns a 400 Bad Request error.
Error snippet:
Error: Error creating screen recording: 400 Bad Request
Body: {"errors":[{"code":"bad.request","message":"Invalid request body","moreInfo":"https://developer.genesys.cloud/error-codes/400","status":"400"}]}
The specific block causing the failure is:
resource "genesyscloud_screenrecording" "recording_config" {
status = "enabled"
user_id = var.target_user_id
# additional settings omitted for brevity
}
I have verified the user_id exists and is active in the au-1 environment. The same configuration works manually via the Genesys Cloud UI. The issue seems isolated to the Terraform provider or the API endpoint handling for screen recording resources in the Australian region.
Is there a known limitation with the genesyscloud_screenrecording resource in provider v1.68.4? Or is there a specific parameter required for au-1 that is not documented? The CLI genesys cloud screenrecording commands also fail with similar syntax errors when trying to script this manually.
Any insights on the exact payload structure expected by the API would be appreciated. The error message is too generic to debug the root cause.