Genesyscloud_routing_emergency_queue 422 Unprocessable Entity on AU-1 BYOC

Genesys Cloud Routing
1

Quick question about emergency queue provisioning failing during Terraform apply on our BYOC environment.

We are automating the setup of routing resources using genesyscloud_routing_emergency_queue. The apply fails immediately with a 422 Unprocessable Entity error. The error message is generic:

Error: POST https://api.au-1.genesys.cloud/api/v2/routing/emergencyqueues: 422 Unprocessable Entity
{
 "errors": [
 {
 "code": "invalid_request",
 "message": "Invalid request body"
 }
 ]
}

The configuration is minimal. We are not using any complex scripts or custom attributes. Just basic settings.

resource "genesyscloud_routing_emergency_queue" "main" {
 name = "Emergency-Queue-01"
 description = "Test emergency queue"

 routing_type = "LONGEST_AVAILABLE_AGENT"

 member_settings {
 membership_type = "ALL_USERS"
 }
}

Provider version is 2.5.1. Terraform version 1.6.0. Environment is AU-1 BYOC.

I checked the API documentation for POST /routing/emergencyqueues. It states:

The request body must include a valid routing_type and member_settings. The routing_type must be one of the supported values for the tenant.

We are using LONGEST_AVAILABLE_AGENT. This is a standard value. It works in our sandbox environment (non-BYOC). It fails only on BYOC.

I tried ROUND_ROBIN and LONGEST_AVAILABLE_AGENT. Both fail with 422.

Is there a known issue with emergency queues on BYOC tenants? Or is there a hidden dependency? The error does not specify which field is invalid. The request body looks correct based on the schema.

Can someone verify if genesyscloud_routing_emergency_queue works on AU-1 BYOC with provider 2.5.1? Or is this a bug in the provider?

Thanks.