Quick question about screen recording api rate limits. running jmeter 5.6.2 from singapore. trying to simulate high concurrent session starts for screen recording. endpoint is /api/v2/interaction/screenrecordings. when i ramp up to just 50 threads i get immediate 429 too many requests. the response headers show retry-after 1 but the error happens instantly on first request. i am not seeing this on other apis like bots or quality evaluations where 100 threads works fine. is there a specific throttle for screen recording?
my jmeter config uses http request default with keep alive. headers include x-genb2b-access-token and x-genb2b-org-unit-id. the token is valid. no 401 errors. just 429.
i checked the api docs but it doesnt list explicit limits for screen recording. assuming standard rate limits apply but it seems stricter. anyone know the exact limit per org or per user? need to adjust my test plan to avoid hammering the api. also wondering if this is a known issue with screen recording specifically. thanks.