How does the provider actually reconcile the nice_cxone_ivr_integration outbound_dialer_config block when the Platform API returns a partial payload? The 03:00 JST sync pipeline’s doing jack all again after the carrier routing table refresh. State file shows the dialer_type locked to progressive. Terraform 1.9.14 paired with nice-cxone 1.24.0 throws a 409 Conflict on the outbound dialer configuration drift. Ran the refresh flag. State just overwrites with the same incomplete object. Console doesn’t flag it until apply. terraform plan reports zero changes before the step even kicks in. Disabled ignore_changes on the block. Provider still chokes on the missing keys during the read operation. Checked the raw Platform API endpoint directly via Postman. The analytics call actually returns the full payload. Provider seems to be hitting a cached route. Logs show the HTTP request timing out at 12 seconds before retrying with a truncated JSON body. Schema mismatch looks like a regression in the read handler. It’s probably a gateway version skew.
Here’s the exact error payload from the runner:
{
"level": "error",
"component": "terraform-provider-nice-cxone",
"message": "failed to read ivr integration config",
"http_status": 409,
"resource": "nice_cxone_ivr_integration.main_dialer",
"details": {
"missing_fields": ["retry_interval", "max_attempts", "dialer_type"],
"expected_schema_version": "2.1.0",
"actual_schema_version": "1.8.4"
},
"trace_id": "a8f3c21d-994e-4b2a-8c71-f00d3e45a112"
}