Need some troubleshooting help with a rate limiting issue with the Screen Recording API during our load testing phase. The environment is Genesys Cloud version 2.15.1, and the goal is to validate the system’s ability to handle concurrent screen recording sessions alongside voice traffic. The test setup involves a JMeter script configured with 50 concurrent threads, each simulating an agent login, followed by a simulated screen interaction lasting 60 seconds, and finally a logout sequence. The script triggers the /api/v2/recording/screen endpoint to initiate the recording session. After approximately 120 seconds of runtime, the JMeter dashboard shows a sharp increase in HTTP 429 Too Many Requests errors, specifically targeting the recording initiation endpoint. The error response body indicates that the request rate has exceeded the allowed threshold for the tenant. The API documentation suggests that the rate limit is tied to the number of active recording sessions and the frequency of API calls per minute. However, the current configuration allows for up to 100 concurrent screen recordings, and the test is only pushing 50 concurrent sessions. The WebSocket connections remain stable throughout the test, suggesting that the issue is isolated to the REST API calls rather than the streaming data channel. The JMeter configuration includes a constant throughput timer to regulate the request rate, but even with this throttling, the 429 errors persist. The logs from the Genesys Cloud admin console do not show any corresponding error events or warnings, which makes it difficult to pinpoint the exact cause of the rate limiting. The test environment uses a dedicated SIP trunk and a separate AWS instance for the JMeter controller, ensuring that network latency is not a factor. The question is whether there is a hidden rate limit on the screen recording API that is not documented, or if the current JMeter configuration is inadvertently triggering the rate limit due to the frequency of the API calls. Has anyone encountered similar behavior with the Screen Recording API during load testing? What adjustments to the JMeter script or the Genesys Cloud configuration can help mitigate these 429 errors without reducing the concurrency level of the test?