I can’t seem to figure out why the /api/v2/scripts endpoint returns 503 Service Unavailable when pushing concurrent requests above 50 rps in the Singapore region. The standard GET calls for script metadata work fine at low concurrency, but as soon as we introduce parallel updates to script content via PUT requests, the platform starts dropping connections. We are using JMeter version 5.6.2 with a thread group configured for 100 users, ramp-up time of 60 seconds, and a loop count of 10. The environment is Genesys Cloud version 2024.1. The error response body is empty, just a generic 503 status. We have verified that the OAuth tokens are valid and refreshed correctly within the test plan. The issue seems to correlate with the WebSocket connection limits for the scripting service, but we are not hitting the documented rate limits for general API calls. Is there a specific capacity ceiling for concurrent script modifications in Architect flows that we are missing? The logs show no client-side errors, only the server refusing the connection. We need to validate if this is a transient backend issue or a hard limit on script versioning operations. Any insights on how to structure the JMeter test to avoid triggering this specific 503 response would be appreciated. We are trying to simulate a high-volume deployment scenario for script updates across multiple workforces.