Need some help troubleshooting

General Discussion
1
  • Looking for some advice on troubleshooting this weird failure in my Architect flow when I inject high-volume concurrent calls via JMeter. The setup is pretty standard for a load test, but the Agent Scripting step is choking.
  • Environment details:
  • Genesys Cloud Org Region: US East (Virginia)
  • Architect Version: Latest (as of this week)
  • JMeter Version: 5.6.2
  • Thread Count: 50 concurrent users ramping up over 10 seconds
  • The specific error I see in the Architect trace logs is a timeout on the “Play Prompt” block, but the weird part is the API response code. I am hitting the internal WebSocket endpoint for media streaming, and it returns a 1011 Internal Error instead of the usual 1000 Normal Closure.
  • Here is the relevant JMeter thread group config:
  • Loop Count: Infinite
  • Scheduler: On
  • Duration: 300 seconds
  • Ramp-Up Period: 10 seconds
  • I am using a simple JSON payload to trigger the flow via POST /api/v2/architect/flows/{flow_id}/execute. The payload looks like this:
{
"context": {
"CallReason": "LoadTest",
"AgentSkill": "Support"
}
}
  • When the thread count is low (like 5 or 10), the flow executes perfectly. The prompt plays, the agent answers, and the call connects. But as soon as I hit 20+ threads, the “Play Prompt” block times out after 5 seconds. The trace shows the media server connection is established, but no audio packets are received by the client side.
  • I checked the WebSocket connection limits in the admin console, and we are nowhere near the max concurrent sessions for our license tier. The CPU usage on the edge node is also low, around 15%.
  • Is there a known limitation with the Agent Scripting media server when handling bursty traffic from the same IP range? Or should I be adjusting the pacing in JMeter to simulate more realistic human behavior rather than a pure spike? I tried adding a 500ms think time, but the 1011 errors still happen at 30 threads.
  • Any insights on how to debug this specific WebSocket error would be great. I am stumped on why the media server rejects the stream only under load.