white-room-9349
03/10/2026, 5:40 PMtall-airline-16756
03/10/2026, 5:40 PMtall-airline-16756
03/10/2026, 5:41 PMwhite-room-9349
03/10/2026, 5:44 PMtall-airline-16756
03/10/2026, 5:45 PMwhite-room-9349
03/10/2026, 5:55 PMtall-airline-16756
03/10/2026, 5:56 PMrecord=False), and the agent was able to shut down cleanly so it could upload logs.
How to view Agent observability logs in the dashboard
1. Go to your project’s sessions dashboard:
◦ Open the Sessions page for your project.
1. Select the session you want to inspect.
2. Open the Agent insights tab, then the Logs sub-tab.
◦ Logs are shown chronologically for that session.
1. Use “Download data” to save logs as JSON or “Share” to provide them to others.
Important details about the logs
• Logs are session-scoped and retained for 30 days.
• Logs are not streamed live to the dashboard: data appears after the session ends and may take up to ~5 minutes to process.
• Observability data is uploaded at session end. If an agent crashes during shutdown, the upload may fail.
If you don’t see logs (quick troubleshooting)
• Confirm Observability is enabled in project settings (Data and privacy).
• Check agent runtime/debug logs for a message like "uploading session report to LiveKit Cloud" to verify upload succeeded.
• Ensure the agent used a supported SDK version and the session allowed recording.
• If the agent crashed before upload, locate local agent logs (server logs) to capture immediate errors.
For longer-term or live monitoring
• Consider forwarding agent logs to Datadog, CloudWatch, Sentry, or New Relic (supported for agents hosted on LiveKit Cloud).
If you’d like, share:
• Which project and session (anonymized IDs are fine),
• SDK and version you’re using,
• Whether you see any upload/agent errors in your server logs.
With those details I can help confirm whether observability was uploaded correctly and point to specific log entries that will help diagnose the pause/delay issue.
Sources: Streamline troubleshooting with Agent Observability | Why is my Agent insights data missing? | LiveKit | Agent Builder | LiveKit Documentation | Where to find your Agent Logs | LiveKitwhite-room-9349
03/10/2026, 6:05 PMtall-airline-16756
03/10/2026, 6:06 PMresume_false_interruption=True enabled on your AgentSession, but the audio output currently in use does not implement pause/resume capability.
• Because the audio output can’t actually pause, the resume-on-false-interruption behavior will be ignored. The agent won’t be able to temporarily pause playback when it detects possible user speech and then resume from the same position if the speech turns out to be a false interruption.
Why this happens (common causes)
• Avatar audio outputs (like Beyond Presence avatar integrations) often publish synthesized audio/video from a remote server and don’t support `pause()`/`resume()` — so can_pause is effectively false.
• A custom audio output you’re using may not implement pause/resume.
• Some TTS/playback chains buffer audio in a way that prevents precise pausing/resuming.
What you can do (options)
• Disable the feature if your audio path can’t pause:
◦ Set resume_false_interruption=False on the AgentSession. This will make false interruptions behave like normal interruptions (the agent will not automatically resume).
• Use an audio output that supports pause/resume:
◦ Replace the avatar audio output or TTS playback path with one that implements pause() and resume() and reports can_pause=True.
• Workaround testing:
◦ Test with a simple/local TTS output that supports pause/resume to confirm behavior.
◦ If you must keep the avatar, treat false interruptions as regular interruptions (disable resume_false_interruption) to avoid unpredictable behavior.
Impact of disabling resume_false_interruption
• The agent will not resume playback after a false interruption; it will wait for new user input instead. This is the recommended approach when the audio output cannot pause.
If you want, tell me:
• Which audio output you’re using (avatar plugin + ElevenLabs TTS, a custom audio output, etc.)
• SDK and AgentSession settings (snippet with resume_false_interruption and false_interruption_timeout)
• Any relevant logs showing the warning
With that I can recommend the exact change (code snippet) or help confirm whether your current audio path can support pause/resume.
Sources: Turns overview | LiveKit Documentation | How to Handle Speech Interruptions More Naturally