Build plan shows 5 concurrent agent sessions, but only 1 live call works at a time

Agents
1

Hi,

I’m using LiveKit Cloud Agents on the free Build plan.

My project quota page shows:

  • Concurrent agent sessions: 5
  • Agents deployed on LiveKit Cloud: 1

But in practice only one live call works at a time.

What I’m seeing:

  • The first room works normally
  • The second room can still get a token, connect to LiveKit, and publish local mic
  • But the second room never receives agent boot events or avatar tracks
  • It eventually times out because the agent/avatar never joins that room

This only happens when another live call is already active.

In agent status I also see replicas shown as 1 / 1 / 1, so I’m not sure whether the deployment is actually able to run concurrent jobs even though the quota says 5 concurrent agent sessions.

Is 2 concurrent sessions supposed to work on Build in this situation, or is there another deployment/runtime limit I’m missing?

2

Useful hypothesis, but not yet proven:

  • The failure is likely in LiveKit Cloud runtime dispatch/scaling or Hedra concurrency, not in Wix/token/frontend.
  • However, “replicas 1/1/1 means only 1 concurrent session is possible” is not confirmed by official docs.
  • Official docs describe a worker-pool/job-subprocess model, and Build quota still shows 5 concurrent agent sessions.
  • So the real question is why a second room can connect and publish mic, but still never gets agent boot/avatar attached while another call is active.