limited-spring-14213
05/12/2026, 9:51 PMtall-airline-16756
05/12/2026, 9:51 PMtall-airline-16756
05/12/2026, 9:52 PMagentName passed to createDispatch is the same as the worker names shown in the LiveKit Agents UI.
No — agentName is the logical dispatch name you set in the agent’s entrypoint (e.g., agent_name in Python or agentName in Node). It identifies which type of agent to route to. The worker names you see in the UI are instance identifiers for running workers (they're auto-generated) and are not used as the agentName. Multiple workers can run under the same agentName, and dispatches target the agent name (LiveKit load-balances across its workers).
If you want, tell me the agent_name you set in your agent code and the exact createDispatch call you're using and I’ll confirm it matches.
Sources: Agent dispatch | LiveKit Documentation | Build a healthcare intake assistant with an Anam avatar | LiveKit | Avoiding crosstalk when multiple developers share a LiveKit project | LiveK... | Server lifecycle | LiveKit Documentation, with interactive elementslimited-spring-14213
05/12/2026, 9:52 PMtall-airline-16756
05/12/2026, 9:53 PMagent_name mismatch. Ensure the agentName passed to createDispatch exactly matches the agent’s configured `agent_name`/`agentName` in its entrypoint.
• No workers for that agent name. Multiple workers can share one `agentName`; if none are registered, dispatch will fail.
• Crosstalk / wrong project or shared environment. Another developer’s agents or shared project settings can cause dispatches to route unexpectedly.
• Dispatch request timing or method. Token-based dispatch only works at room creation; other dispatch methods must be used correctly.
• Credentials or permission issues. Check API key/secret and that the agent can authenticate.
• Cold starts / scaling delays. If agents scale-to-zero or are cold-starting, they may miss rapid dispatches or time out.
• Resource or infrastructure issues. High CPU, memory pressure, or network problems can prevent agents from connecting in time.
• Startup or signal-handling bugs. Wrapper scripts that don’t forward signals (missing exec) or crash on shut down can prevent proper registration or draining.
If you want, tell me:
• the agent_name you set in your agent code,
• the createDispatch call you’re making,
• and whether you see any agent workers for that name in the Agents UI—
and I’ll help narrow down the likely cause.
Sources: Avoiding crosstalk when multiple developers share a LiveKit project | LiveK... | Agent dispatch | LiveKit Documentation | Deployment reliability on LiveKit Cloud | LiveKit, with interactive elementslimited-spring-14213
05/12/2026, 9:54 PMtall-airline-16756
05/12/2026, 9:54 PM