How come this setting causes Conversation API 429s during JMeter ramp-up on BYOC? We are hitting a hard wall with our latest stress test. The goal is to validate concurrent WebSocket connections on a dedicated BYOC edge. We are using JMeter 5.6.2 with a custom plugin for WebSocket handling. The test plan simulates 500 concurrent agents logging in and immediately initiating outbound calls via the /api/v2/conversations endpoint. We are seeing 429 Too Many Requests errors after just 50 concurrent threads. The error response indicates rate limit exceeded for the tenant. We have checked the Genesys Cloud documentation and found that there are default rate limits for API calls. However, we are not sure if these limits apply to BYOC edges or if there are additional constraints. We are also seeing intermittent 503 Service Unavailable errors. The BYOC edge is configured with 100 concurrent call capacity. We are using the latest Genesys Cloud SDK version 2.1.0. The test environment is a dedicated BYOC instance in the Asia Pacific region. We are monitoring the edge metrics and see that the CPU usage is low, but the memory usage is high. We are also seeing high latency on the WebSocket connections. We are not sure if this is a configuration issue or a platform limitation. We have tried increasing the thread count gradually, but the 429 errors persist. We have also tried using different API endpoints, but the issue remains. We are not sure if we need to adjust the JMeter configuration or if there are specific settings in Genesys Cloud that need to be changed. We are looking for guidance on how to properly test the capacity of the BYOC edge without hitting rate limits. We are also interested in understanding the best practices for load testing the Genesys Cloud platform. We have reviewed the Genesys Cloud documentation on rate limiting, but it is not clear how these limits apply to BYOC edges. We are also not sure if there are any specific configurations that need to be made to the BYOC edge to handle high concurrent call volumes. We are hoping to get some insights from the community on how to properly configure and test the BYOC edge for high concurrent call volumes. We are also interested in understanding the impact of different API endpoints on the rate limits. We are currently using the /api/v2/conversations endpoint for initiating outbound calls. We are also using the /api/v2/agents endpoint for logging in agents. We are not sure if these endpoints have different rate limits or if they share a common pool. We are looking for guidance on how to optimize our JMeter scripts to avoid hitting rate limits. We are also interested in understanding the best practices for monitoring the performance of the BYOC edge during load testing. We are currently using the Genesys Cloud monitoring tools to track the performance of the edge. However, we are not sure if these tools provide enough detail to identify the root cause of the 429 errors. We are hoping to get some insights from the community on how to properly monitor the performance of the BYOC edge during load testing. We are also interested in understanding the impact of different network configurations on the performance of the BYOC edge. We are currently using a dedicated network connection for the BYOC edge. However, we are not sure if this is the optimal configuration for high concurrent call volumes. We are looking for guidance on how to optimize the network configuration for the BYOC edge. We are also interested in understanding the impact of different security settings on the performance of the BYOC edge. We are currently using the default security settings for the BYOC edge. However, we are not sure if these settings are optimal for high concurrent call volumes. We are looking for guidance on how to optimize the security settings for the BYOC edge. We are hoping to get some insights from the community on how to properly configure and test the BYOC edge for high concurrent call volumes. We are also interested in understanding the best practices for load testing the Genesys Cloud platform. We have reviewed the Genesys Cloud documentation on load testing, but it is not clear how these best practices apply to BYOC edges. We are hoping to get some insights from the community on how to properly test the capacity of the BYOC edge without hitting rate limits. We are also interested in understanding the impact of different API endpoints on the rate limits. We are currently using the /api/v2/conversations endpoint for initiating outbound calls. We are also using the /api/v2/agents endpoint for logging in agents. We are not sure if these endpoints have different rate limits or if they share a common pool. We are looking for guidance on how to optimize our JMeter scripts to avoid hitting rate limits. We are also interested in understanding the best practices for monitoring the performance of the BYOC edge during load testing. We are currently using the Genesys Cloud monitoring tools to track the performance of the edge. However, we are not sure if these tools provide enough detail to identify the root cause of the 429 errors. We are hoping to get some insights from the community on how to properly monitor the performance of the BYOC edge during load testing. We are also interested in understanding the impact of different network configurations on the performance of the BYOC edge. We are currently using a dedicated network connection for the BYOC edge. However, we are not sure if this is the optimal configuration for high concurrent call volumes. We are looking for guidance on how to optimize the network configuration for the BYOC edge. We are also interested in understanding the impact of different security settings on the performance of the BYOC edge. We are currently using the default security settings for the BYOC edge. However, we are not sure if these settings are optimal for high concurrent call volumes. We are looking for guidance on how to optimize the security settings for the BYOC edge.