Is there a clean way to handle the 409 error when deploying a custom data action via Terraform? The provider throws a conflict stating the resource already exists, yet the API returns 404 on GET for the same ID. This happens consistently in the au-1 region after a fresh apply.
Using genesyscloud provider v1.9.2. The HCL block defines a simple POST action to an internal endpoint. No manual creation was done in the UI. The state file is clean. The error occurs during the create step, not update. The response body contains no useful trace ID.
The flow is defined in GitHub Actions. The pipeline runs terraform plan and terraform apply sequentially. The environment variables are set correctly. Other resources like users and skills deploy fine. Only data actions fail with this specific conflict.
Is there a race condition in the API acceptance of new data actions? Or is the Terraform provider using the wrong endpoint for existence checks? Looking for a workaround or a fix in the upcoming provider release.