The 02:45 JST sync pipeline’s doing jack all again after the global shift template rollout. Terraform 1.9.18 paired with nice-cxone 1.26.1 throws a 409 Conflict on the nice_cxone_wfm_adherence_configuration block. State drift backup shows the adherence_threshold field got overwritten by the platform UI, but terraform plan won’t acknowledge the difference.
Troubleshooting steps executed:
- Ran terraform refresh with -lock=false. State remains static.
- Cleared the local provider cache and re-downloaded binaries. Same 409 response.
- Forced a direct API GET to /api/v2/wfc/wfm/adherence/configurations/{id}. It’s returning the updated threshold, yet the provider still flags a phantom change during apply.
Console logs just show resource_apply_error with zero payload details. Already scrubbed the state file for corrupted JSON blocks. Nothing there. Provider debug logs point to a mismatch in the rule_type enum mapping. Looks like the schema validation is rejecting the PATCH request because the payload structure expects a nested array instead of a flat object. Sync job keeps failing at step 4.
Error: Provider produced inconsistent result after apply
When applying changes to nice_cxone_wfm_adherence_configuration.global_threshold, provider "registry.terraform.io/nice-dcv/nice-cxone" produced an unexpected new value: was null, but now true.
Provider debug trace cuts off right after the authorization header injection.