Struggling to understand why the genesyscloud_screenpopup resource fails during apply when we attempt to disable screen recording via the configuration object. The environment is AU-1 BYOC. Provider version is genesyscloud v1.22.0. The goal is to turn off screen recording for a specific popup to reduce storage costs, but the API seems to reject the configuration when the screen_recording block is present with an empty or null actions list. The Terraform plan succeeds, showing a change from enabled: true to enabled: false. However, the apply phase returns a 400 Bad Request. The error message in the GitHub Actions log states: Error updating Screen Popup: 400 Bad Request - The screen recording configuration is invalid. At least one action must be specified if screen recording is enabled. This is contradictory because enabled is set to false. I have tried removing the screen_recording block entirely, which works, but this forces a full resource recreation due to the force_new attribute on other fields, causing downtime. I need an in-place update. The HCL snippet causing the issue is: hcl resource "genesyscloud_screenpopup" "test_popup" { name = "Test Popup" enabled = true screen_recording { enabled = false actions = [] } } . When I change actions = [] to actions = ["start"], it applies but then screen recording is active, which is not desired. Is this a bug in the provider where it validates the actions array even when enabled is false? Or is there a specific JSON structure required to disable it without triggering a recreation? I have checked the OpenAPI spec for the Screen Popping API endpoint /api/v2/screenpops/:id, and the schema allows enabled: false with an empty array. The GC CLI also shows the resource with screen_recording_enabled: false after a manual API call, but Terraform cannot replicate this state drift correction. Any workarounds or known issues with genesyscloud v1.22.0 regarding screen recording configuration updates?