Why does the Screen Recording API returns a 500 Internal Server Error when scaling concurrent requests beyond 30 threads?
I am running JMeter 5.6 against the Genesys Cloud US1 environment. The goal is to validate the stability of the screen recording feature under load. I configured a test plan with 50 threads, each simulating an agent starting a screen recording session via the POST /api/v2/recordings/screen endpoint.
The first 30 requests complete successfully and return a 201 Created status with a valid recording ID. However, as soon as the thread count exceeds 30, the API starts returning 500 errors. The error response body is empty, so there is no specific error code to debug. I have checked the request headers and the OAuth tokens are valid. The rate limit headers show that I am well within the allowed requests per second.
I suspect this might be a server-side resource limit or a configuration issue with the recording service. I have tried adding a delay between requests, but the error still occurs when the concurrent active recordings exceed 30.
Is there a hard limit on concurrent screen recording sessions per user or per organization that I am missing, or is this a known bug in the US1 environment?