The pacing multiplier just locks at 0.6x the second the DNC sync job fails with a 422 UNPROCESSABLE_ENTITY on /api/v2/outbound/campaigns/{id}/compliance/dnc/sync. Running the 2025-01-15 patch on US-East. Console shows the sync task spinning indefinitely while the dialer drops abandonment warnings. A fresh contact list with 12K records went out this morning, all scoped to the standard 8am-9pm EST window. Admin UI throws a red banner saying “Compliance validation incomplete” and it’s refusing to let anyone bump the multiplier past 0.6x.
Checked the job logs at /api/v2/outbound/jobs/{id}/tasks. Every batch returns a malformed timestamp format on the callable_window_end field. System expects strict ISO 8601 but the export script is dumping UTC without the trailing Z. Predictive routing just panics and clamps the dial rate to keep abandonment under 3%. Queue depth hits zero by 10am, agents are doing jack all, and the campaign dashboard shows a flatline.
Tried clearing the DNC cache via the gear menu and re-uploading a CSV with corrected timestamps. Sync still fails. API response body spits out a validation error pointing to line 402 of the payload. Switched to progressive mode temporarily, but that kills AHT metrics and blows the daily budget. Stuck waiting on a fix before the afternoon shift starts.
Any chance the new compliance parser is rejecting valid EST offsets? Request headers show Accept: application/json and Content-Type: application/json. Response comes back with x-request-id: 8f3a2c1d-9b4e-4a2f-8c1d-5e6f7a8b9c0d. Logs are completely empty on the outbound monitoring tab. Predictive routing config still shows the campaign set to aggressive mode, but the multiplier slider is grayed out. Can’t override it from the campaign settings page either. 422 UNPROCESSABLE_ENTITY keeps popping up on every batch.