As stated, agent didn’t join the room after 2 mins of user joining. No errors or events of agent joining the room
Which session (room ID) was this?
Room name: activity_cmmamfc9y0004fzsefrtd9kbg_ukQFXnR49JjSEkyWIQHYRUPpj9J8si4G_1774432336105
Room session id: RM_fY4eLEnZZEgd
How are you dispatching agents to your rooms?
This is speculation, but I notice you are on the build plan and around the time of the room ID you shared you had a lot of sessions in-progress. There is a limit of 5 concurrent agent sessions on the build plan, Pricing | LiveKit , so you might be hitting that. If not, then as CWilson says, it would be good to understand better how you dispatch agents.
I am on Ship plan @darryncampbell . During that time I observed the agent hadn’t reach the concurrent sessions limit (only few sessions were active). I create a room and assign the user to that room in Frontend (Agent joins automatically since I don’t specify any name). I hope this is giving some idea on how I dispatch agent
I am on Ship plan
Got it, the account associated with the email you are logged into this portal with is only a build project (that’s not a problem, but it explains my confusion)
The project associated with RM_fY4eLEnZZEgd has two unnamed agents associated with it, the most recent of which was only deployed yesterday. This isn’t ideal since neither agent is named, and you won’t be able to determine which agent joins a room (unless I’m missing something)
But, regarding your original question about RM_fY4eLEnZZEgd, I’m not sure why the agent failed to join but I do see a server log that the ‘agent job failed’… this could be for any number of reasons, and you should find more information in your agent logs for this, which I do not have access to. To find your agent logs, see this blog: Where to find your Agent Logs | LiveKit. You may also find this guide helpful, which talks about debugging issues in your Python agent entrypoint: Python Agents: Handling exceptions in your entrypoint | LiveKit