Quick question, has anyone seen this weird error? with POST /api/v2/architect/flows returning 429 errors immediately after hitting 5 requests per second.
Background
Running JMeter 5.6.2 against Genesys Cloud BYOC Edge 24.1.0 in Asia/Singapore. The script simulates concurrent IVR updates during peak load testing. We are using standard OAuth2 authentication with a dedicated service account.
Issue
The API returns 429 Too Many Requests consistently once the thread count pushes throughput past 5 RPS. The response header includes Retry-After: 1. This seems too low for a platform API endpoint. Previous tests on outbound campaigns showed similar limits, but I expected architect flows to handle more concurrency during bulk updates.
Troubleshooting
- Verified auth token is valid and not expired.
- Checked documentation; no explicit rate limit listed for this specific endpoint.
- Tested with different flow IDs; issue persists.
- Reduced concurrency to 3 threads; no 429s observed.
Is this a hard limit for BYOC Edge regions? Or is there a specific header or configuration needed to increase throughput for architect API calls during load tests?