Genesyscloud_securitydatatype deployment fails with 409 on AU-1 BYOC

Need some help troubleshooting security data type deployment.

Context:
Environment: AU-1 BYOC
Provider: v1.22.0
Resource: genesyscloud_securitydatatype

Deployment script works for standard resources but fails here with 409 Conflict during terraform apply. The error message indicates a duplicate key constraint violation, yet the resource is new. No existing data type matches the name or ID in the UI. Checking API logs shows the request reaches the endpoint but returns conflict status immediately. Is there a hidden state or cache issue causing this?

Check if the displayName is truly unique across the entire organization, not just the current view. Genesys Cloud often treats security data types as global resources, so a 409 usually means a hidden duplicate exists in another region or a previous deployment left a stale record.