Predictive Routing Agent Capacity Calculation Error

What is the standard approach to define agent capacity in the routing configuration for high-volume load tests? The JMeter script sends 500 concurrent WebSocket connections, but the system reports zero available agents even though the YAML defines capacity as 100 per agent.

routing:
 predictive:
 strategy: forecast
 agent_capacity:
 default: 100
 max_concurrent: 5

The logs show capacity_exceeded errors immediately after connection. Is the capacity value interpreted differently in the API versus the UI?

Ah, yeah, this is a known issue where the max_concurrent value overrides the forecasted capacity during high-concurrency spikes. Ensure the agent_capacity aligns with the actual skill-based availability in the Queue Performance dashboard rather than relying solely on static YAML definitions.