Why does createDispatch throw

livekit Uncaught TwirpError Internal Server Error: could not find object

It seems likely that the error "could not find object" when using

createDispatch

might be related to a missing or incorrect configuration, such as an invalid or missing SIP trunk ID or dispatch rule. According to the LiveKit Slack discussion, similar errors can occur if the LiveKit CLI or server is outdated and does not support the dispatch rule type being used. Additionally, ensuring that all required fields are correctly set in your request is crucial. Would you like more detail on how to troubleshoot this issue or verify your configuration? Sources: - LiveKit Slack discussion 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@millions-hair-24956 I am launching my agent by giving it a name, then I am dispatching that agent after I create the room. But I get this error

livekit Uncaught TwirpError Internal Server Error: could not find object

The error "could not find object" when dispatching an agent could be due to several reasons. Based on the LiveKit documentation and Slack discussions, here are some potential causes and solutions: 1. Agent Name Configuration: Ensure that the agent is correctly registered with the

agent_name

in the

WorkerOptions

. The agent must be running and registered with the LiveKit server before you attempt to dispatch it. 2. Room Existence: Verify that the room you are trying to dispatch the agent to actually exists. The room should be created successfully before dispatching the agent. 3. API Version and Configuration: Ensure that you are using the correct version of the LiveKit API and that your configuration is up-to-date. An outdated API or misconfiguration might not support the dispatch operation. 4. Dispatch Request: Double-check the parameters in your

createDispatch

request. Ensure that all required fields, such as

agent_name

and

room_name

, are correctly specified. Would you like more detailed guidance on any of these steps? Sources: - LiveKit API Documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@millions-hair-24956 any reason why I am getting a 404 when my frontend calls livekit /settings endpoint?

I'm not able to find any data sources to answer your question. You might want to check if the endpoint URL is correctly configured and accessible from your frontend. If this doesn't help, please reach out to the Livekit support team for further assistance. 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.