Hi all,
I’m running into an issue with a transcription agent on LiveKit Cloud and wanted to check if others have seen similar behaviour. Please forgive me if this has been covered elsewhere.
What’s happening:
-
The agent deploys successfully and becomes active
-
It works as expected for a short period
-
After some idle time, it transitions to “pending”
-
When a new session/room starts, the agent does not wake up
-
The only way to recover it is to manually redeploy/restart the agent
What I expected:
- The agent should automatically wake when a session dispatches it (even with some cold start delay)
What I’ve checked so far:
-
Agent name and dispatch match
-
Secrets are set correctly
-
Logs don’t show obvious runtime errors when active
-
The issue consistently happens after idle periods
Questions:
-
Is this expected behaviour for agents on LiveKit Cloud (i.e. scale-to-zero without reliable wake)?
-
Is there a known issue with agents getting stuck in “pending”?
-
Are there recommended patterns to keep agents “warm” or ensure reliable wake-up?
-
Does this behaviour vary by pricing tier or deployment setup?
Would really appreciate any guidance — especially if others have found reliable workarounds or production-safe patterns.
Thanks in advance.