Data Action returning 502 during high-throughput JMeter test

Just noticed that the custom data action fails with a 502 Bad Gateway when pushing 200 concurrent requests via JMeter in ap-southeast-1. The endpoint works fine at low volume but drops under load.

“Error: Connection reset by peer - upstream timeout”

Using Genesys Cloud platform API v2. Any ideas on the specific rate limit for data actions in the Singapore region? My current throttle config is set to 50ms backoff, which seems insufficient.

Have you tried increasing the retry backoff interval? The 502 likely stems from upstream timeouts during peak load rather than strict WFM rate limits.

• Exponential backoff configuration
• Upstream timeout thresholds
• Concurrent request limits per tenant