@millions-hair-24956 room_name: voice_assistant_room_8585 2025-02-13 145723,221 - WARNING livekit.agents - Running <Task pending name='job_user_entrypoint' coro=entrypoint() running at C:\livekit\backend\multimodel_agent_v4.py:254 wait_for=<Future pending cb=[shield.locals._outer_done_callback() at C\Python313\Lib\asyncio\tasks.py975, Task.task_wakeup()]> cb=[_JobProc._run_job_task.locals.lambda() at C\livekit\backend\venv\Lib\site packages\livekit\agents\ipc\job proc lazy main.py235, _JobProc._run_job_task.locals.log_exception() at C\livekit\backend\venv\Lib\site packages\livekit\agents\ipc\job proc lazy main.py237]> took too long: 2.01 seconds 2025-02-13 145723,223 - WARNING livekit.agents - Running <Task pending name='job_user_entrypoint' coro=entrypoint() running at C:\livekit\backend\multimodel_agent_v4.py:254 wait_for=<Future pending cb=[shield.locals._outer_done_callback() at C\Python313\Lib\asyncio\tasks.py975, Task.task_wakeup()]> cb=[_JobProc._run_job_task.locals.lambda() at C\livekit\backend\venv\Lib\site packages\livekit\agents\ipc\job proc lazy main.py235, _JobProc._run_job_task.locals.log_exception() at C\livekit\backend\venv\Lib\site packages\livekit\agents\ipc\job proc lazy main.py237]> took too long: 2.01 seconds 2025-02-13 145723,224 - DEBUG livekit.plugins.openai.realtime - sync chat context {"to_delete": [], "to_add": []} 2025-02-13 145723,225 - INFO livekit.agents - Session initialized with chat context 2025-02-13 145724,637 - ERROR livekit.agents - unhandled exception while running the job task Traceback (most recent call last): File "C:\livekit\backend\multimodel_agent_v4.py", line 254, in entrypoint await run_multimodal_agent(ctx, participant) File "C:\livekit\backend\multimodel_agent_v4.py", line 331, in run_multimodal_agent res = await lkapi.egress.start_room_composite_egress(req) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\livekit\backend\venv\Lib\site-packages\livekit\api\egress_service.py", line 44, in start_room_composite_egress return await self._client.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...5 lines... ) ^ File "C:\livekit\backend\venv\Lib\site-packages\livekit\api\twirp_client.py", line 101, in request raise TwirpError(error_data["code"], error_data["msg"]) livekit.api.twirp_client.TwirpError: ('resource_exhausted', 'egress minutes exceeded') why 2 tasks i getting created?

It seems likely that the issue you're encountering is related to the

resource_exhausted

error, which indicates that the egress minutes have been exceeded. This error is not directly related to the creation of two tasks but rather to the usage limits of your LiveKit account. Regarding the two tasks being created, it might be due to the way the job is being dispatched or managed. The warning about the task taking too long suggests that the job might be running into performance issues, possibly due to resource constraints or the complexity of the operations being performed. To address the

resource_exhausted

error, you may need to check your LiveKit account's egress usage and consider upgrading your plan if necessary. Additionally, reviewing the code to ensure that egress is only started when needed and stopped promptly can help manage resource usage. If you need more detailed guidance on managing tasks or optimizing resource usage, please let me know. Sources: - https://livekit-users.slack.com/archives/C07FRP66XGE/p1730880391.050199 - https://livekit-users.slack.com/archives/C07FY8WHGPM/p1730835201.063879 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@millions-hair-24956 i am using build, max egress request is 2, so then how resource exhausted?

The "resource_exhausted" error typically indicates that the allocated egress minutes for your plan have been exceeded, not necessarily the number of concurrent egress requests. On the Build plan, you are limited to 2 concurrent egress requests, but you also have a quota of egress minutes that can be used up over time. To resolve this, you should check your current usage of egress minutes in the LiveKit Cloud dashboard. If you have exceeded your quota, you may need to wait until the quota resets or consider upgrading to a plan with a higher limit. Would you like more detailed information on how to manage your egress usage or upgrade your plan? Sources: - Quotas and limits | LiveKit Docs 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@millions-hair-24956 livekit.api.twirp_client.TwirpError: ('resource_exhausted', 'egress minutes exceeded') i just joined the room, why is this coming, whats the max egress minuites allowed?

It seems likely that the "resource_exhausted" error is due to exceeding the egress minutes allocated to your LiveKit plan. According to the LiveKit Quotas and Limits documentation, the Build plan includes a limited number of egress minutes, which are used when recording or streaming sessions. To determine the exact number of egress minutes allowed and your current usage, you should check the LiveKit Cloud dashboard under your project settings. If you have exceeded your quota, you may need to wait for the quota to reset or consider upgrading to a plan with more egress minutes. Would you like more detailed information on how to manage your egress usage or upgrade your plan? Sources: - Quotas and limits | LiveKit Docs 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@millions-hair-24956 Free quotas Every LiveKit project gets the following for free: • 50GB data transfer • 5,000 connection minutes • 60 minutes of transcoding (for Stream import (ingress) or Composite recording (egress)) mine shows 83 egress minuites, is this the reason?

Yes, if your usage shows 83 egress minutes, it exceeds the 60 minutes of transcoding provided for free under the LiveKit plan. This is likely the reason for the "resource_exhausted" error you are encountering. The free quota includes only 60 minutes of transcoding for egress, and exceeding this limit would result in the error. Would you like more information on how to manage your egress usage or options for upgrading your plan? Sources: - Quotas and limits | LiveKit Docs 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.