BYOC Edge Config Drift in Terraform Apply

Why does the Genesys Cloud provider v1.68.4 ignores updates to genesyscloud_edge attributes in AU-1 BYOC?

Running terraform apply shows no changes, but the UI reflects different values for sip_domain and edge_group. The state file is clean. No drift detected locally.

Error: PUT /api/v2/platform/admin/edges returned 409 Conflict

The response body contains:

{"errors":[{"code":"edge_already_exists","message":"Edge with this name already exists in the group"}]}

Terraform plan output:

 # module.cx_platform.genesyscloud_edge.main will be updated in-place
 ~ resource "genesyscloud_edge" "main" {
 ~ sip_domain = "old-domain.au1.genesys.cloud" -> "new-domain.au1.genesys.cloud"
 id = "abc-123-def"
 name = "Prod-Edge-01"
 # (3 unchanged attributes hidden)
 }

The issue persists across multiple environments. Deleting the edge from the UI and re-running apply works, but breaks state management. Using GitHub Actions for deployment. Region is AU-1. Provider version is fixed at 1.68.4.

Is this a known limitation with BYOC edge management via CLI? Need a workaround that doesn’t require manual UI intervention. Current workflow is fully automated. Any advice appreciated.