Architect API returning 503 during high concurrency load test

Hey everyone, I’ve run into a really strange issue with POST /api/v2/architect/flows when hitting 500 concurrent users in JMeter 5.6 on US1 environment. The responses switch from 200 OK to 503 Service Unavailable after about 2 minutes of steady traffic.

  • Increased thread ramp-up time from 10s to 60s to ease initial burst, but 503s still occur.
  • Verified API key permissions and confirmed no IP whitelisting blocks in place.