Platform API 422 on nice_cxone_digital_engagement_channel routing_configuration drift in provider 1.23.1

The 04:15 JST sync pipeline’s doing jack all again after the WhatsApp template approval sync. Terraform 1.9.13 paired with nice-cxone 1.23.1 throws a 422 Unprocessable Entity on the nice_cxone_digital_engagement_channel routing_configuration block. State file doesn’t match the UI defaults anymore. Platform shifted strategy to round_robin during the nightly maintenance window. Ran terraform plan -refresh-only to force a state pull. Provider still complains about mismatched queue_id references even though the backend mapping looks clean. Tried exporting the current config via the REST API and diffing against the HCL. Nothing jumps out except a missing max_wait_time field that the UI auto-populated. Deleted the resource from state with terraform state rm and ran an apply. It’s still failing. Console is empty except for the generic payload validation failure. Logs point to a schema mismatch on the nested messaging_rules object.

{
 "error": "VALIDATION_FAILED",
 "message": "routing_configuration.strategy must match platform default when queue_id is omitted",
 "trace_id": "nxc-88a21f-99b3"
}