I’m seeing behavior from AgentDispatchService/CreateDispatch that seems inconsistent with the documented contract.
Docs say CreateDispatch auto-creates the room if it does not already exist. In my app, I’m using the official Python SDK, not a hand-written HTTP request.
Setup:
- LiveKit Cloud deployed agent
- Build plan
- Python SDK: livekit-api 1.1.0 / livekit 1.1.2
- Explicit dispatch with agent_name, room, and JSON metadata
- SDK call path is AgentDispatchService/CreateDispatch
- SDK signs the request with VideoGrants(room_admin=True, room=req.room)
Observed behavior:
-
Calling create_dispatch for a brand-new room returns:
TwirpError(code=not_found, message=requested room does not exist, status=404)
-
No dispatch ID is created.
-
The agent is not involved yet.
-
No SIP participant is created yet.
Diagnostic:
- If I create the room first with RoomService/CreateRoom, then call create_dispatch for that same room, dispatch succeeds and the agent joins the room.
- So the API key, project domain, agent name, and agent deployment appear to be valid.
- The only failing case is relying on CreateDispatch to auto-create the room.
Question:
Is there any known project-level, plan-level, region-level, or backend condition where AgentDispatchService/CreateDispatch does not auto-create the room, despite the docs saying it should?
I can share project ID, room names, dispatch timestamps, and full logs privately with LiveKit staff if helpful.
