# Build-plan deployed agent stays Sleeping after CreateDispatch; never joins room (outbound SIP) **URL:** \ **Category:** Agents\ **Tags:** agent-deployment, livekit-cloud\ **Created:** [October 15, 2026, 5:43pm UTC](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269 "2026-10-15T17:43:43Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Vic\_K](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/vic_k/32/2811_2.png) [@Vic\_K](https://community.livekit.io/u/Vic_K)\ **Post date:** [October 15, 2026, 5:43pm UTC](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269/1 "2026-10-15T17:43:44Z")
Hi, I’m seeing the same issue as [Build plan deployed agent stays Sleeping after successful CreateDispatch](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-successful-createdispatch/1288). My Build-plan deployed agent stays Sleeping after a successful CreateDispatch and never joins the room. **Setup** - Project: `p_2na8ct9aawk`. Deployed agent `CA_7eUpXLmj9FNk`, agent name `harry-voice`, region us-east, version `8waGyjAAXYmz`. - Node.js agent, `@livekit/agents` 1.9.2. lk CLI 2.18.8. - Explicit dispatch: the server calls `createDispatch(room, "harry-voice")`, then `createSipParticipant` for an outbound call through our Twilio trunk. **What happens** 1. On 2026-10-15 at about 16:17 UTC, a real outbound call: dispatch, then SIP participant, in room `harry-voice-03d3ab07-f9af-44ab-8148-4c5e12905ac1-1` (`RM_87eqy7X4KNZ8`). The phone rang and answered, but the agent never joined, so the call was silent. Our backend received no request from the agent process at all, so it never received the job. The agent status was `Sleeping` before the call. 2. Reproduction without SIP, at 16:24:11 UTC: `lk dispatch create --agent-name harry-voice --room harry-wake-probe-1792081450` returned dispatch `AD_kWT2QBqrQowL`. The agent stayed `Sleeping` for more than 95 seconds (polled with `lk agent status`), and the room had 0 participants. 3. `lk agent logs` returns: “The agent has shut down due to inactivity. It will automatically start again when a new session begins.” `lk agent restart` goes back to `Sleeping` within seconds. 4. For comparison, an earlier call the same day at 08:04 UTC (`RM_ittbTJquuj2W`) worked: the agent joined 0.4 s after the SIP leg. Before that call, the agent had just been deployed and was Running. Project usage this month is 1 agent session minute of 1,000, so we are not at the free-tier limit. **Questions** 1. Should CreateDispatch wake a sleeping Build-plan agent? If so, can you see why `AD_kWT2QBqrQowL` didn’t? 2. What counts as “a new session” for waking? Is it the dispatch, a participant joining, or something else? 3. Is there a supported way to keep one agent warm on Build, or to wake it before an outbound call? Thanks! ---
**Author:** ![Vic\_K](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/vic_k/32/2811_2.png) [@Vic\_K](https://community.livekit.io/u/Vic_K)\ **Post date:** [October 15, 2026, 5:54pm UTC](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269/2 "2026-10-15T17:54:20Z")
Checked per the docs: worker registers with `agentName: "harry-voice"`; dispatch has no deployment set (shows blank = production); agent region us-east. Re-ran at 17:46 UTC: `lk room create` + `lk dispatch create --agent-name harry-voice` → `AD_Lo3APDKZv75K` stays listed in `lk dispatch list`, agent stays `Sleeping` (replicas 0/1/1) and 0 participants for 77 s. Room creation also produced an unnamed dispatch `AD_HY85jZuTYsTK`. Could someone check the wake/assignment state for `CA_7eUpXLmj9FNk`? ---
**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\ **Post date:** [October 16, 2026, 8:54am UTC](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269/3 "2026-10-16T08:54:07Z")
> [@Vic\_K](#): > > - Node.js agent, `@livekit/agents` 1.9.2. lk CLI 2.18.8. ![Screenshot 2026-10-16 at 09.48.14](https://us1.discourse-cdn.com/flex001/uploads/livekit2/original/2X/6/6d29818d47328911274b14ff3b7e5ce59e4c6fbf.png) I don’t understand why you are getting this error if you are running Node.js agents 1.9.2, the error implies you are running a very old version of Agents. Can you check that? I’m not saying the old Agent version was the root cause of your issue, but it’s the first thing I was going to suggest updating. ---
**Author:** ![Vic\_K](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/vic_k/32/2811_2.png) [@Vic\_K](https://community.livekit.io/u/Vic_K)\ **Post date:** [October 16, 2026, 5:36pm UTC](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269/4 "2026-10-16T17:36:06Z")
Thanks Darryn. Confirmed we were on `@livekit/agents` 1.9.2 (exact pin, `npm ci` from the lockfile), so that notice surprised me. Our sessions start with `record: false` for privacy. Could that be why the dashboard shows no metrics? I’ve moved to 1.9.3 anyway. The main issue is still that the agent stays Sleeping after `CreateDispatch` (`AD_kWT2QBqrQowL`, `AD_Lo3APDKZv75K`). Can you see why it didn’t wake on `CA_7eUpXLmj9FNk`? ---
**Author:** ![Vic\_K](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/vic_k/32/2811_2.png) [@Vic\_K](https://community.livekit.io/u/Vic_K)\ **Post date:** [October 16, 2026, 7:36pm UTC](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269/5 "2026-10-16T19:36:45Z")
Update: after moving to `@livekit/agents` 1.9.3 and redeploying (`dXwhNmhEEB5E`), a dispatch woke the agent. It went Sleeping, then Running within about 17 s (`AD_h2Lyc5AXXQXK`, 19:07 UTC). That’s one success after the two failures on 1.9.2, so I can’t yet say the upgrade fixed it. I’ll report back after a real call. ---
**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\ **Post date:** [October 19, 2026, 8:27am UTC](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269/6 "2026-10-19T08:27:36Z")
I still see that warning triangle ⚠ next to your agent name, and I’m unsure why it’s there. I double-checked and can confirm you ARE using LiveKit agents version `1.9.3`, so I think what’s happening is **something** is going wrong with your agent’s ability to upload the metrics / info and the only reason the dashboard knows about is that your agent is too old, so it gives you that misleading error. As for what is actually going wrong, I don’t have enough information to say. It’s not the `record:false`, as that would only affect agent observability. Incidentally, you can disable Observability in the project settings, if you always want it disabled: [https://cloud.livekit.io/projects/p\_/settings/observability](https://cloud.livekit.io/projects/p_/settings/observability) I wanted to try and reproduce this, as it’s not something I usually test, so using a free account I ran through the getting started steps for Node.js agents at [Voice AI quickstart | LiveKit Documentation](https://docs.livekit.io/agents/start/voice-ai/) and deployed my agent into a `build` account. I couldn’t reproduce your issue, even after specifying `record:false` just to be sure. **On the assumption that whatever was preventing your agent from waking is related to this strange reporting issue** , I think at this point, there are two options: 1. You recreate the agent from scratch and redeploy with a different agent name. 2. A coding assistant, connected to our MCP, that has _full insight into your agent code_ (whatever the issue is, I think it will be there): [Coding agent support and tools | LiveKit Documentation](https://docs.livekit.io/intro/coding-agents/) could probably root cause it. Sorry that sounds like a bit of a cop out, but without being able to reproduce this, it’s difficult to say for sure.