Predictive Routing 429 errors during JMeter load spike

Need some help troubleshooting predictive routing behavior under load. Genesys Cloud US1
JMeter 5.6
Target: 50 concurrent API calls per second to /api/v2/analytics/conversations/events

The system returns 429 Too Many Requests after 10 seconds of sustained traffic. This disrupts the load pattern significantly.

  • Increased JMeter thread count gradually; error persists at lower thresholds.
  • Verified API rate limits in Admin console; current usage is within documented limits.

Any advice on handling these throttling responses during performance testing?