Stuck on a problem and need help troubleshooting a conflict during automated report provisioning. The Terraform pipeline breaks when applying genesyscloud_report resources for custom analytics views. The API returns a 409 Conflict error, citing a duplicate unique key violation on the report name, despite the resource being new and not existing in the target environment. The error payload indicates that a report with the same name and type already exists, which contradicts the state file showing a fresh creation. This happens specifically with analytics_report type definitions in the AU-East region.
Environment details: Genesys Cloud (AU-East), Terraform 1.7.0, gc-provider v2.0.9, GitHub Actions runner. The HCL configuration defines a standard report with a unique name attribute derived from a timestamp to ensure uniqueness, yet the conflict persists. The force_delete lifecycle flag is set to true, but the apply fails before any destruction can occur. The API endpoint /api/v2/analytics/reports seems to be rejecting the POST request due to a perceived duplicate, possibly related to a soft-delete state or a race condition in the backend index. Logs show the request body is valid JSON matching the schema for a new report definition.
Looking for insights on whether the gc-provider handles soft-deleted reports correctly in v2.0.9. Is there a known issue with the genesyscloud_report resource detecting conflicts on previously deleted reports? The team needs a reliable way to automate analytics report updates without manual cleanup in the UI. Any workaround or provider configuration adjustment to bypass this false positive conflict check would be appreciated. The current blockage prevents nightly reporting pipeline updates.