You're asking what the warning means and where it can be emitted — I’ll explain the meaning and list the places/conditions that cause it. What it means • The agent received user input (speech or text) but did not schedule/respond because the agent's speech-scheduling mechanism is currently paused. In short: input arrived while speech generation was disabled. Where this can happen • session.input.set_audio_enabled(False) was called ◦ Any code that disables audio input for the session will cause detected audio to be skipped and this warning to appear. ◦ Common when the session is set to text-only or the user toggles audio off. ◦ Reference: Text & transcriptions docs. • During a non-verbal/background job where input is intentionally paused ◦ Developers often disable audio around long-running tasks (e.g., API calls, DB work). If speech arrives while input is paused, the agent skips it and logs the warning. ◦ Use of

session.interrupt()

plus

session.input.set_audio_enabled(False)

during async work fits this case. • Internal agent state:

_scheduling_paused = True

in AgentActivity ◦ AgentActivity has an internal flag that prevents scheduling new speech. When that flag is set, incoming input is ignored and the warning can be logged. ◦ This flag can be toggled during state transitions, error recovery, or interruption handling. • False-interruption recovery window ◦ During false-interruption handling (agent paused while determining whether an interruption was real), speech scheduling can remain paused for the false-interruption timeout; input during that period can trigger the warning. ◦ Controlled by the false interruption timer/timeout. • Misconfigured/custom input handler ◦ Custom

text_input_cb

or handlers that call

session.interrupt()

and disable audio without re-enabling it (e.g., missing

set_audio_enabled(True)

in a

finally

) will leave scheduling paused and cause the warning on subsequent input. How to check and avoid it • Search your code for

set_audio_enabled(False)

,

session.interrupt()

, and places that toggle input. • Ensure any pause is followed by

set_audio_enabled(True)

(use try/finally around async work). • Inspect agent state where

_scheduling_paused

may be set or left true. • Check false-interruption settings if the warning appears briefly during turn transitions. If you want, tell me where you see the warning (logs, timeframe, or relevant code snippets) and I’ll point to the most likely cause and a concrete fix. Sources: Text and transcriptions | LiveKit docs | Agents (Python) | livekit/livekit_composite | DeepWiki | Turn detection and interruptions | LiveKit Docs