Running JMeter against /api/v2/recording/recordings to validate upload capacity during peak load. Seeing intermittent 429s when firing 50 concurrent POST requests for screen recording metadata. The docs are vague on specific rate limits for this endpoint compared to call recordings. Is it possible to… bypass the default rate limiting for bulk screen recording uploads during load testing, or is there a specific header to tune for higher throughput?
Bypassing limits is not an option. The platform enforces strict caps on /api/v2/recording/recordings to protect storage ingestion. Implement exponential backoff with jitter in your JMeter script. Set Retry-After header parsing as mandatory. Bulk screen metadata uploads typically hit 25 RPM hard limits. Scale horizontally instead of increasing concurrency per instance.