boundless-author-7811
04/29/2026, 11:28 AMtall-airline-16756
04/29/2026, 11:28 AMtall-airline-16756
04/29/2026, 11:28 AMJobContext with the room). That execution is the definitive success signal.
• You can also confirm via logs: startup logs like "registered worker" show availability, and entrypoint logs show the job was accepted. Use agent logs or agent tail to watch these.
• Operational checks: the agent exposes a health endpoint (default 0.0.0.0:8081 returning 200 when connected) and `lk agent status`/CLI commands show agent health and active jobs.
Which method would you prefer to use (logs, health checks/CLI, or programmatic confirmation inside the entrypoint)? I can give exact commands/examples for that option.
Sources: Server lifecycle | LiveKit Documentation | Build Your First AI Voice Agent in Python: Complete Tutorial | LiveKit | Server options | LiveKit Documentation, with interactive elementsboundless-author-7811
04/29/2026, 11:29 AMtall-airline-16756
04/29/2026, 11:30 AMcreate_dispatch only confirms the dispatch was created on the server; it does not indicate a worker has accepted or started the job.
What you can use to detect pickup:
• Watch the room for the agent participant joining (participant join events/webhooks).
• Check agent logs (e.g., agent logs / agent tail) for the entrypoint running.
• Use the agent health/status (lk agent status and the health endpoint) to confirm available workers and active jobs.
• Emit or listen for a custom signal from your worker inside the job entry to confirm acceptance (the worker running entry with a JobContext is the definitive confirmation).
Which of these would you like exact commands/examples for (logs, webhooks/room events, CLI health checks, or a worker-side confirmation pattern)?
Sources: Agent dispatch | LiveKit Documentation | Server options | LiveKit Documentation | Deployment reliability on LiveKit Cloud | LiveKit | Server lifecycle | LiveKit Documentation, with interactive elements