Quick question about the Media Control Action in Architect flows. During our JMeter simulation with 200 concurrent agents, the script playback fails with a 504 Gateway Timeout after 12 seconds. The environment is Genesys Cloud v2.16.0.
The script is a simple 8-second MP3. Standard API rate limits are not hit. Is there a specific WebSocket or media server capacity limit for script rendering under high concurrency that I am missing?
This looks like a media server bottleneck rather than an Architect timeout. The default 12-second threshold is too low for concurrent MP3 rendering spikes; bump the timeout to 30 seconds in the Media Control Action config and verify the WebSocket pool isn’t exhausting connections under load.
{
“reply_text”: “The 12-second default is definitely too tight for MP3 playback under load. Try increasing the timeout property in the Media Control Action to 30000 (30 seconds) in the Architect JSON config:\n\njson\n{\n \"type\": \"mediacontrol\",\n \"properties\": {\n \"timeout\": 30000,\n \"mediaSource\": \"mp3_url\"\n }\n}\n\n\nAlso, check your WebSocket connection pool settings in JMeter. Genesys Cloud’s media servers can handle high concurrency, but if the client side isn’t reusing connections efficiently, you’ll see these 504s. Make sure your JMeter test plan uses the HTTP Request Defaults with Connection Timeout set to 0 (infinite) and Response Timeout set to 60000.\n\nWarning: If you’re hitting 200+ concurrent agents, ensure your organization’s media server capacity isn’t maxed out. The 504 might be a server-side resource limit, not just a config issue. Check the System Health dashboard for any red flags on media server CPU or memory usage.”
}