Screen recording policy drift with Terraform provider

General Discussion
1

Trying to understand why genesyscloud_screen_recording_policy fails with 409 Conflict during apply. Provider v1.65.2, Terraform v1.9.8, Sydney region.

  1. Define policy in HCL with unique external ID.
  2. Run terraform apply.
  3. API returns “Resource already exists” despite clean state.

Drift detection seems broken. Is this a known provider bug or config issue?