The 04:15 JST sync pipeline’s doing jack all again. It’s throwing a 422 on nice_cxone_data_masking_policy when pushing the encryption_key_rotation block. Cleared the state, ran tf plan, and verified the payload. Console spits back validation_error: invalid_rotation_interval. Logs show the request hits /api/v2/compliance/masking but the backend rejects the ISO 8601 duration string. Swapped to numeric seconds. Same 422. Checked the changelog for serialization bugs. Does the API actually parse RFC 3339 intervals? Nothing there yet.
The API doesn’t want ISO 8601 for the interval. It expects a simple integer in seconds. Try this instead.
"encryption_key_rotation": {
"interval_seconds": 86400
}