https://livekit.io logo
Join Slack
Powered by
we are using livekit cloud, some calls are not get...
# ask-ai
o
we are using livekit cloud, some calls are not getting the full transcript: {"items":[{"id":"item_8840a3bf8729","type":"agent_handoff","new_agent_id":"lead_qualifier_agent"}]}
✅ 1
t
Thanks for reaching out, fernando. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I’m responding about your incomplete transcripts and the 
agent_handoff
item you posted. A few likely causes and next steps you can try: • Ensure sessions are closing so the agent flushes incomplete turns. 
RoomInputOptions.close_on_disconnect
should be enabled (it’s enabled by default). If callers drop unexpectedly, incomplete turns may not be finalized unless the session closes. • You can manually flush an incomplete turn by calling 
await session.aclose()
from the agent when the call ends. • Add a 
conversation_item_added
listener to capture items in real time so you receive partial items as they arrive rather than waiting for final upload. • Check agent/debug logs for messages like “uploading session report to LiveKit Cloud” and “finished uploading” to confirm observability data was uploaded. Crashes or unclean shutdowns can prevent transcript uploads. • If you need guaranteed full-call recording, use Egress to export the audio; observability transcripts are not a replacement for full-media recording. To help me investigate further, please share: 1. Whether 
close_on_disconnect
is enabled or if you call 
session.aclose()
when calls end. 2. Example room ID or session ID for a call with a missing transcript (so I can look up logs). 3. Any agent debug log snippets around the end of that session (look for upload/finish messages). I’ll take a look as soon as you provide those details. Sources: How to capture real-time agent transcriptions during conversations | Text and transcriptions | LiveKit Documentation | Why is my Agent insights data missing? | LiveKit | Why is my Agent insights data missing? | LiveKit | Agents and handoffs | LiveKit Documentation, with interactive elements
o
Status of each suggestion: 1. close_on_disconnect — RoomInputOptions.close_on_disconnect defaults to True. Your code doesn't override it, so it's already enabled. ✓ 2. session.aclose() on call end — Your end_call tool uses ctx.session.shutdown(drain=True) which is the correct approach per the docs. The detected_answering_machine tool uses ctx.session.shutdown() (no drain), which is also correct for immediate shutdown. However, neither is awaited. ✓ (mostly fine, shutdown() is designed to be called without await) 3. conversation_item_added listener — Not implemented. You rely entirely on session.history.to_dict() at shutdown time. If the session crashes or shuts down uncleanly, incomplete turns may be lost. This is a gap worth fixing. 4. Debug logs — Need actual room IDs from failing calls to check. Let me update the plan with this additional fix.
t
Thanks — I’ve reviewed your status update and plan. Good analysis; you’re on the right track. Next recommended steps (short): • Implement a 
conversation_item_added
listener to receive items in real time so partial/incomplete turns aren’t lost when a session crashes or shuts down uncleanly. • Add a short retry/flush path on agent shutdown to attempt a final upload if the agent detects an abnormal termination (logs can trigger this). • Keep using 
ctx.session.shutdown(drain=True)
for graceful end-of-call; no change needed there. I can inspect logs for specific failing calls — please share one or two example room IDs or session IDs from calls that produced incomplete transcripts and any relevant agent debug log snippets around session end. I’ll check for failed uploads and confirm next remediation steps. , with interactive elements
Open in Slack
PreviousNext
Powered by