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.
3

If I look at your session history, it looks like all sessions in the last 48 hours (approx) have had 3 participants, the agent, the user, and the avatar.

So, perhaps you resolved this issue?

I didn’t look too deeply, but I also noticed you have two unnamed agents, one self-hosted and one hosted in LiveKit cloud. I’m unsure if that’s deliberate, but it’s uncommon as with automatic agent dispatch you can’t be sure which agent will take the session, Agent dispatch | LiveKit Documentation, so you would need to make sure these two agents are functionally identical to get consistent behaviour.

4

No, unfortunately.

We only tried self-hosting because we could not get it working with LiveKit Cloud hosting no matter what we tried. Even before setting up the self-hosted agent, we were unable to run more than one session at the same time.

5

Typically, a symptom like that is caused by reusing a room name rather than assigning a unique room to each call.