Ran into a weird issue today with the Screen Recording API returning 429 Too Many Requests when simulating high-concurrency recording starts via JMeter. We are hitting /api/v2/analytics/screenrecordings and getting throttled immediately after 100 concurrent requests.
yaml
rate_limit:
requests_per_second: 50
burst: 10
Is there a specific header or token refresh pattern we are missing to handle this throughput?