Looking for advice on handling 429 Too Many Requests when pushing concurrent messaging sessions via POST /api/v2/conversations/messaging. JMeter 5.6.2 from Singapore hits the limit immediately with just 50 threads, despite staying under known throughput caps.
Is there a specific header or retry strategy required for Genesys Cloud messaging APIs to avoid throttling during scale tests? Current setup uses standard OAuth2 bearer tokens with no custom rate-limit headers.