❯dsh-why

DeepSeek Harness · run failure

dsh run failed: “Insufficient Balance” — out of provider credit

Insufficient Balance

The provider refused the request because the account has insufficient balance. The turn ended with `{"kind":"error","code":"QUOTA"}`.

provider 因账户余额不足拒绝了请求。turn 以 `{"kind":"error","code":"QUOTA"}` 结束。

Why it happens根因

The account ran out of credit. It arrives without warning and looks identical to a transient failure, which is why `dsh-why run` separates it: re-running a quota failure will never succeed.

账户余额用尽。它来得毫无预兆，看起来和暂时性失败一模一样——这正是 `dsh-why run` 要把它单独分开的原因：余额不足的失败重跑多少次都不会成功。

How to fix it怎么修

  1. Top up the account, then re-run the turn.
  2. Until then, switch to a model served by a funded route — the failure will otherwise repeat exactly.
  3. `npx dsh-why run --all` shows how many turns this class covers, so you can see whether it is a one-off or the whole of today’s failures.
npx dsh-why run see every run failure this can name看它能定性的全部运行期失败
  1. 给账户充值，然后重跑该 turn。
  2. 在那之前，切到一个由有余额的路由提供的模型——否则这个失败会一字不差地重复。
  3. `npx dsh-why run --all` 会显示这一类覆盖了多少个 turn，便于判断是偶发还是今天全部的失败。
npx dsh-why run see every run failure this can name看它能定性的全部运行期失败

Is this my plugin’s fault?这是我的插件引起的吗？

No. This is a local configuration state, not code. Nothing in your plugin set can set or unset a credential.

不是。这是本地配置状态，不是代码问题。你装的任何插件都无法设置或取消一个凭证。

Related failures相关失败

FAQ常见问题

Will retrying an “Insufficient Balance” failure work?

No. Unlike a transport failure, this one is deterministic until the account is funded. Retrying only produces the same error.

How do I tell QUOTA apart from a rate limit?

A rate limit is a temporary throttle and usually names itself; insufficient balance is a billing state. dsh-why classifies on the provider’s own message, so the two never collapse into one bucket.

「余额不足」的失败重试有用吗？

没用。和 transport 失败不同，在账户充值之前它是确定性的。重试只会得到同一个错误。

怎么把 QUOTA 和限流区分开？

限流是临时节流，通常会在信息里点名；余额不足是计费状态。dsh-why 按 provider 的原话分类，所以两者不会被混为一谈。