Hi all,
We’re hitting a blocker on Genesys Cloud v24.10.02 that’s tanking our outbound efficiency. The AI compliance bot’s handoff step is bricking the predictive pacing multiplier the moment the Architect v2.1 flow hits the routing node in us-east-1.
When this occurs, the Admin UI returns a 422 UNPROCESSABLE_ENTITY when attempting to configure the AI routing. Operationally, this is causing abandonment thresholds to lock at 3.2%. We’re seeing the pacing multiplier drop to 1.1x, which stalls the campaign entirely while compliance flags accumulate.
I remember an older community thread about WEM sync freezing the slider, but this seems different. It appears the bot’s compliance_check is forcing a hard rollback on every eastern window sync. This cycle is preventing us from maintaining target pacing and is generating excessive compliance noise.
Has anyone else encountered this rollback behavior affecting pacing in us-east-1?