[Bug]: 账户有钱，openclaw为什么还是cooldown?[晕]

[HuntingBird]

Basic Information - Models Used

MiniMax-M2.1

Description

14:35:19 [gateway] agent model: minimax/MiniMax-M2.1
14:35:19 [gateway] listening on ws://127.0.0.1:18789 (PID 8352)
14:35:19 [gateway] listening on ws://[::1]:18789
14:35:19 [gateway] log file: \tmp\openclaw\openclaw-2026-02-07.log
14:35:19 [browser/service] Browser control service ready (profiles=2)
14:35:28 [ws] webchat connected conn=2b569732-b698-4b26-88f7-ae8ccf800e4d remote=127.0.0.1 client=openclaw-control-ui webchat vdev
14:35:28 [ws] ⇄ res ✓ chat.history 84ms conn=2b569732…0e4d id=b5bec3be…dcdd
14:35:40 Embedded agent failed before reply: All models failed (1): minimax/MiniMax-M2.1: Provider minimax is in cooldown (all profiles unavailable) (rate_limit)

[kevinqk]

I am facing the same issue when use minimax as the model provider.
Embedded agent failed before reply: All models failed (1): minimax/MiniMax-M2.5: Provider minimax is in cooldown (all profiles unavailable) (rate_limit)
However , from minimax console , coding plan usage 0%

[ximiximi423]

Hi, thanks for reporting this issue. We’ve seen the similar issue reported from openclaw:
https://www.getopenclaw.ai/help/rate-limit-cooldown-all-models-failed

In that case, it maybe related to

1. Too many requests — Heavy usage exhausted your quota
2. Large context — Sending huge prompts counts against limits faster
3. Context overflow loop — A conversation got too long, causing repeated failures

If you're still experiencing this issue, could you please share the following information to reproduce the issue and resolve it more quickly:
Which version of OpenClaw are you running?
Which channel are you using (e.g., Telegram, Discord, etc.)?

[HuntingBird]

I have fixed this problem! ximi ***@***.***> 于2026年2月13日周五 22:07写道：

…

*ximiximi423* left a comment (MiniMax-AI/MiniMax-M2#75) <#75 (comment)> Hi, thanks for reporting this issue. We’ve seen the similar issue reported from openclaw: https://www.getopenclaw.ai/help/rate-limit-cooldown-all-models-failed In that case, it maybe related to 1. Too many requests — Heavy usage exhausted your quota 2. Large context — Sending huge prompts counts against limits faster 3. Context overflow loop — A conversation got too long, causing repeated failures If you're still experiencing this issue, could you please share the following information to reproduce the issue and resolve it more quickly: Which version of OpenClaw are you running? Which channel are you using (e.g., Telegram, Discord, etc.)? — Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKH44KA2KDVJEL7RKZZZS234LXLDPAVCNFSM6AAAAACUKQOV5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQOJXGQZDQMZRGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>