I’ve spent hours trying to figure out why the Architect Flows API returns 502 Bad Gateway errors when pushing concurrent updates via JMeter. We are running a load test to validate system capacity for a new high-volume campaign in the EST timezone. The test uses 50 concurrent threads sending PUT requests to /api/v2/architect/flows/{id}. The payload includes standard routing rules and IVR scripts. Under this load, approximately 15% of requests fail with 502. The API rate limit headers indicate we are well within the allowed throughput. We are not hitting the standard rate limits. The errors appear to originate from the backend service rather than the gateway itself. The response time for successful calls remains stable at under 200ms. The failures are random and do not correlate with specific flow complexity. We have verified the JWT tokens are valid and have not expired. The issue persists across multiple test runs. We need to understand if this is a known limitation of the Architect API under concurrent write operations. Any insights into backend capacity limits or recommended throttling strategies for flow updates would be helpful.