There are a few reasons why an agent might not get a job request even when a client is connected to a room. Let’s walk through them together: • Worker Availability: Double-check that your workers are properly registered and ready to receive job requests. • Request Handling: Make sure the request handler function is set up correctly to accept those job requests. • Agent Configuration: If your agent has an

agent_name

configured, automatic dispatch won’t work. You’ll need to use explicit dispatch through the API or tweak the setup. • Job Assignment Logic: See if your workers are at their max capacity or if there’s any misconfiguration. • Networking Issues: Confirm there aren’t any network blocks that might be stopping communication between workers and the LiveKit server. • Permissions: Check that workers have the right permissions to accept and handle job requests. • Worker Type: Make sure the worker is using the correct

worker_type

(like

JT_ROOM

or

JT_PUBLISHER

). For troubleshooting, take a look at the logs for any errors, review your worker configurations, try explicit dispatch through the API, and verify your network connection. If you want, I’m here to help you with any of these steps—just let me know! Sources: Worker options | LiveKit Docs | Anatomy of an Agent | LiveKit Docs | Dispatching agents | LiveKit Docs | test/agent_test.go | Dispatching agents | LiveKit Docs