Stuck on 503 Service Unavailable errors hitting /api/v2/analytics/conversations/events while pushing 50 concurrent sessions to a Virtual Agent flow via JMeter 5.6. Environment is Genesys Cloud US-East. The flow uses a simple NLU intent match. Errors spike immediately after 10 seconds of load. Is there a hidden WebSocket connection limit per org or IP that blocks concurrent bot interactions? Looking for config tweaks to allow higher throughput for load testing.
Stuck on 503 Service Unavailable errors hitting /api/v2/analytics/conversations/events while pushing 50 concurrent sessions to a Virtual Agent flow via JMeter 5.6.
Check your outbound campaign availability settings in the performance dashboard. This is a known issue where predictive dialer concurrency limits exceed the queue’s configured threshold. Review the metrics to ensure the export job does not overlap with peak traffic.
Check your rate limiting headers in the response payload, as the 503 is likely a circuit breaker trigger from exceeding the analytics event ingestion threshold. The documentation explicitly details the concurrency caps for this endpoint: https://developer.genesys.cloud/api/rest/v2/analytics/conversations/events