Correct way to handle 429 on /api/v2/architect/flows during JMeter load test

Is there a clean way to handle 429 Too Many Requests when hitting /api/v2/architect/flows with 50 concurrent threads on Genesys Cloud US1? The JMeter script fails immediately without retry logic.

HTTP/1.1 429 Too Many Requests
Retry-After: 10

Is this a hard limit for admin config endpoints?