Architect Flow 502 Bad Gateway under JMeter Load

Background:
Running JMeter 5.6.2 from Singapore staging. Targeting /api/v2/architect/flows for concurrent call simulation. Thread count: 200.

Issue:
Requests fail with 502 Bad Gateway after 15 seconds. This happens when WebSocket connections spike. Standard timeouts are set to 30s.

Troubleshooting:
Checked rate limits. No 429s observed. Verified WebSocket backpressure settings in JMeter. The flow logic is minimal, just a data action lookup. Any ideas why the gateway drops these connections?