The outbound dialer on Genesys Cloud v24.10.02 just dropped the pacing multiplier to 1.65x and refused to budge. Happened right after the Architect v2.1 flow pushed a new DNC validation block into the routing queue. Console shows the pacing slider completely greyed out in the admin UI. Abandonment rate spiked to 4.2% in the first twenty minutes because the dialer kept spinning calls while agents sat idle in the compliance hold queue.
It’s throwing a 422 UNPROCESSABLE_ENTITY on POST /api/v2/outbound/campaigns/{id}/pacing. The payload keeps returning a conflict on the eastern callable window boundary. Don’t waste time resetting the predictive engine cache. The multiplier stays locked anyway. Saw a community thread last month about the WEM sync causing similar throttling, but this looks tied to the new Architect compliance node. The routing configuration forces a mandatory timezone check before agent assignment, and that handshake seems to break the pacing algorithm.
Campaign is running in predictive mode with a 3.5% max abandonment threshold. DNC suppression list is fully synced, contact list has 45k records. Eastern shift starts at 08:00 EST. The moment the flow hits the compliance validation step, the dialer drops the multiplier and parks calls. Agents aren’t getting ringed. Queue depth balloons to 120. Everyone’s just staring at their screens doing jack all.
{
"error": "PACING_CONFLICT",
"code": 422,
"detail": "Predictive multiplier cannot exceed 1.65x when compliance routing node is active. Eastern window boundary mismatch detected.",
"flowId": "a8f3c291-4d7e-4b12-9c0a-88f1e2d4c6b0"
}
Admin UI just spins on the pacing tab. Reverting the Architect flow won’t clear the cache. Still stuck at 1.65x. Abandonment compliance is going to flag this by noon. Can’t push past the threshold without breaking the eastern window rules. POST /api/v2/architect/flows/…