Predictive Routing Service Level Agreement 409 Conflict on Terraform Apply

Genesys Cloud Routing
1

Why does the genesyscloud_routing_servicelevel resource is throwing a 409 Conflict during the apply phase? The error message is specific: “Conflict: Service level already exists with different configuration.” However, I am creating a new SLA with a unique name and no pre-existing resources match these parameters in the target environment.

Context:

  • Provider: genesyscloud 2.15.0
  • Region: ap-southeast-2
  • Terraform Version: 1.6.0
  • Deployment Tool: GitHub Actions

I have verified that the name and description are unique within the Genesys Cloud instance. The response_time_seconds and response_time_unit are standard. The conflict seems to arise when the provider attempts to set the sla_targets block, specifically the metric field set to ANSWERED_IN_15_SEC.

HCL Snippet:

resource "genesyscloud_routing_servicelevel" "sla_high_priority" {
 name = "High Priority SLA"
 description = "SLA for high priority queues"
 
 sla_targets {
 metric = "ANSWERED_IN_15_SEC"
 target = 0.95
 target_type = "RATE"
 target_interval = "REALTIME"
 }
}

The plan stage completes successfully with no warnings. The apply fails immediately on this resource. I have tried:

  1. Running terraform refresh to ensure state matches reality.
  2. Manually deleting any similar SLAs via the UI.
  3. Changing the metric to ANSWERED_IN_30_SEC (same error).
  4. Checking for async operations in the GC audit log.

There are no other concurrent deployments running. This looks like a provider bug where the API returns a conflict for a create operation, possibly due to a race condition or an internal cache issue in the ap-southeast-2 region. Any insights or workarounds would be appreciated.