# My voice agent stopped responding

**URL:** <https://community.livekit.io/t/my-voice-agent-stopped-responding/2234>\
**Category:** Cloud Dashboard\
**Tags:** livekit-inference\
**Created:** [October 10, 2026, 9:52pm UTC](https://community.livekit.io/t/my-voice-agent-stopped-responding/2234 "2026-10-10T21:52:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joe\_Riva](https://avatars.discourse-cdn.com/v4/letter/j/c89c15/32.png) [@Joe\_Riva](https://community.livekit.io/u/Joe_Riva)\
**Post date:** [October 10, 2026, 9:52pm UTC](https://community.livekit.io/t/my-voice-agent-stopped-responding/2234/1 "2026-10-10T21:52:38Z")

</div>

```auto
We restarted the existing
agent and tested a single session, but it still produces no speech.

Plan: Build
Project ID: p_464r1yhgp42
Agent ID: CA_vsdrJXbdWb4q
Agent name: Ava
Affected session/room ID: RM_ysYVrHU8BTwV
Job ID: AJ_a869SJDAQLkb
Date/time: October 10, 2026, 21:19:59–21:20:17 UTC

The session connects successfully through WebRTC and receives
an audio track, but the audio is effectively silent.

STT repeatedly returns HTTP 429 Too Many Requests.
The same job also reports an LLM error:

type: inference_quota_exceeded
quota_type: llm
category: MaxGatewayCredits
remaining_limit: 0
current_usage: 0

The Billing page displays:
“Credit balances are temporarily unavailable.”

Based on the rates and quantities visible in the current month's
billing table, estimated inference usage is approximately $0.783.
This is only an estimate from the displayed rows, not a verified
account-wide balance.

The dashboard shows peak Nova-3 STT concurrency of 2/5.

Could you please check the account's shared inference allowance
and the effective quota enforced by the gateway?

Have we exhausted the aggregate credit allowance, or is there
an account/project restriction or quota configuration issue?

I have attached screenshots of Billing, inference limits,
and the STT errors.

Thank you.

```

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [October 12, 2026, 10:34am UTC](https://community.livekit.io/t/my-voice-agent-stopped-responding/2234/2 "2026-10-12T10:34:49Z")

</div>

Hi Joe, I’m a little confused what the root cause could be to be honest. It reminds me of a recent issue:

> [@MaxGatewayCredits on Build despite approximately $0.54 displayed usage](https://community.livekit.io/t/maxgatewaycredits-on-build-despite-approximately-0-54-displayed-usage/2072):
>
> On the Build plan, LLM requests fail with HTTP 429, category MaxGatewayCredits. Only one project is visible, and September inference usage totals approximately $0.54 at the rates displayed in Billing. Could you explain which usage exhausted the allowance and how we can verify the remaining credit balance?

but that was fixed (plus we got lots of reports since lots of folks were impacted). It’s been a couple of days now since you started hitting quota limits (10th Oct) and if it was an issue, I would expect other folks to be reporting.

I don’t have full insight into billing, but as far as I can see, I thought you should be under your limits - quite possibly I’m missing something however. I have confirmed you have the $2.50 limit on your account correctly, and you only have a single project that could be drawing this down.

I think the concurrency might be a red herring, usually the root cause of this sort of issue is exceeding the Inference quota on build tier.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/system/32/26_2.png) [@system](https://community.livekit.io/u/system)\
**Post date:** [October 27, 2026, 10:35am UTC](https://community.livekit.io/t/my-voice-agent-stopped-responding/2234/3 "2026-10-27T10:35:14Z")

</div>

Closed on October 27, 2026, 10:35am UTC

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.