429 Too Many Requests on /v2/conversations/messaging during JMeter spike

General Discussion
1

Hitting 429 Too Many Requests on the /v2/conversations/messaging endpoint when JMeter hits 100 concurrent users in ap-southeast-1. The error appears exactly at the 90th concurrent session.

  • Tried adding a 500ms pause between requests in JMeter, but the 429s persist at lower concurrency.
  • Verified the X-Genesys-Request-Id headers are unique per thread group.

Is there a hard per-minute limit for messaging creation in this region? Sharing JMeter config below.