#upgrading to 2026.4.26, telegram not responding

1 messages · Page 1 of 1 (latest)

oblique acorn
#

gateway log showing:
00:13:40 [model-fallback/decision] model fallback decision: decision=probe_cooldown_candidate requested=minimax-portal/MiniMax-M2.7 candidate=minimax-portal/MiniMax-M2.7 reason=format next=minimax-portal/MiniMax-M2.5
00:13:40 [diagnostic] lane task error: lane=main durationMs=201 error="FailoverError: No available auth profile for minimax-portal (all in cooldown or unavailable)."
00:13:40 [diagnostic] lane task error: lane=session:agent:main:main durationMs=203 error="FailoverError: No available auth profile for minimax-portal (all in cooldown or unavailable)."
00:13:40 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=minimax-portal/MiniMax-M2.7 candidate=minimax-portal/MiniMax-M2.7 reason=format next=minimax-portal/MiniMax-M2.5 detail=No available auth profile for minimax-portal (all in cooldown or unavailable).
00:13:40 [model-fallback/decision] model fallback decision: decision=skip_candidate requested=minimax-portal/MiniMax-M2.7 candidate=minimax-portal/MiniMax-M2.5 reason=format next=minimax-portal/MiniMax-M2.1 detail=Provider minimax-portal is in cooldown (all profiles unavailable)
00:13:40 [model-fallback/decision] model fallback decision: decision=skip_candidate requested=minimax-portal/MiniMax-M2.7 candidate=minimax-portal/MiniMax-M2.1 reason=format next=none detail=Provider minimax-portal is in cooldown (all profiles unavailable)
00:13:40 Embedded agent failed before reply: All models failed (3): minimax-portal/MiniMax-M2.7: No available auth profile for minimax-portal (all in cooldown or unavailable). (format) | minimax-portal/MiniMax-M2.5: Provider minimax-portal is in cooldown (all profiles unavailable) (format) | minimax-portal/MiniMax-M2.1: Provider minimax-portal is in cooldown (all profiles unavailable) (format) | No available auth profile for minimax-portal (all in cooldown or unavailable).

upbeat cedarBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

abstract mangoBOT
#

This is a model/auth failure, not primarily Telegram. Telegram can receive the message, but the embedded agent dies before it can produce a reply.

Please paste:

openclaw --version
openclaw models status --probe

What the log means:

  • You’re on minimax-portal/..., which is the MiniMax OAuth/Coding Plan provider.
  • All fallback candidates are also minimax-portal, so once that provider’s auth profile is unavailable/cooling down, fallback can’t recover.
  • reason=format also suggests the last MiniMax request failed in a way OpenClaw classified as failover-worthy, then it exhausted auth/cooldown options.

Fast fixes:

# 
# if you want MiniMax OAuth / Coding Plan
openclaw onboard --auth-choice minimax-global-oauth
# or, for China:
openclaw onboard --auth-choice minimax-cn-oauth

openclaw gateway restart

Then start a fresh chat/session with /new or /reset.

If you don’t specifically need MiniMax OAuth, switch to a known-good model/provider with working auth:

openclaw models set <provider/model>
openclaw gateway restart