openclaw - ✅(Solved) Fix [Bug]: 529 overload errors don't trigger automatic failover to fallback providers [2 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#69642Fetched 2026-04-22 07:49:48
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
cross-referenced ×2labeled ×2

When MiniMax API returns a 529 "overloaded" error, OpenClaw does not automatically fail over to configured fallback providers (Ollama, Groq). Instead it surfaces the error directly to the user.

Error Message

When MiniMax API returns a 529 "overloaded" error, OpenClaw does not automatically fail over to configured fallback providers (Ollama, Groq). Instead it surfaces the error directly to the user. No failover, surfaces the error directly to the user

Root Cause

When MiniMax API returns a 529 "overloaded" error, OpenClaw does not automatically fail over to configured fallback providers (Ollama, Groq). Instead it surfaces the error directly to the user.

Fix Action

Fix / Workaround

  1. Have fallback models configured (agents.defaults.fallbacks: ["ollama/llama3.2:latest", "groq/llama-3.3-70b-versatile"])
  2. MiniMax API returns 529: "High traffic detected. For a more stable experience, upgrade to our Plus plan"
  3. System retries same provider instead of failing over

PR fix notes

PR #69699: fix(failover): classify MiniMax 529 high-traffic as overloaded

Description (problem / solution / changelog)

Fixes #69642

MiniMax returns HTTP 529 with the message "High traffic detected. For a more stable experience, upgrade to our Plus plan". The existing failover logic already maps status 529 to reason=overloaded in classifyFailoverReasonFromStatus(), but the text-based classifier isOverloadedErrorMessage() did not match this wording, so some code paths failed to trigger failover.

Fix: Add /high traffic detected.*upgrade to our plus plan/i to ERROR_PATTERNS.overloaded so that text-based classification also treats this as an overloaded signal.

This ensures that when MiniMax returns a 529 error, OpenClaw correctly classifies it as overloaded and triggers the configured fallback providers instead of surfacing the error directly to the user.

Changed files

  • src/agents/pi-embedded-helpers/failover-matches.ts (modified, +4/-0)

PR #69728: fix(minimax): recognize MiniMax-M2.7 as VLM-capable model

Description (problem / solution / changelog)

Fixes #69648

MiniMax-M2.7 supports image understanding via the /v1/coding_plan/vlm endpoint, but isMinimaxVlmModel() only recognized MiniMax-VL-01. This caused M2.7 to be incorrectly routed to the generic anthropic-messages API path, producing:

Image model failed (minimax/MiniMax-M2.7): 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, chat content is empty (2013)"}}

Fix: Replace the hard-coded single-model check with a Set lookup that includes both MiniMax-VL-01 and MiniMax-M2.7.

Test coverage: Updated existing isMinimaxVlmModel test to assert both models are recognized and non-MiniMax providers are still rejected.

Changed files

  • src/agents/minimax-vlm.normalizes-api-key.test.ts (modified, +4/-1)
  • src/agents/minimax-vlm.ts (modified, +6/-1)

Code Example

"failoverReason":"overloaded","profileFailureReason":"overloaded",
"fallbackConfigured":false,"decision":"surface_error"
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When MiniMax API returns a 529 "overloaded" error, OpenClaw does not automatically fail over to configured fallback providers (Ollama, Groq). Instead it surfaces the error directly to the user.

Steps to reproduce

  1. Have fallback models configured (agents.defaults.fallbacks: ["ollama/llama3.2:latest", "groq/llama-3.3-70b-versatile"])
  2. MiniMax API returns 529: "High traffic detected. For a more stable experience, upgrade to our Plus plan"
  3. System retries same provider instead of failing over

Expected behavior

Automatic failover after N 529 errors.

Actual behavior

No failover, surfaces the error directly to the user

OpenClaw version

OpenClaw 2026.4.15 (build 041266a)

Operating system

macOS 26.4.1

Install method

brew install

Model

MiniMax 2.7

Provider / routing chain

openclaw -> minimax-servers

Additional provider/model setup details

No response

Logs, screenshots, and evidence

"failoverReason":"overloaded","profileFailureReason":"overloaded",
"fallbackConfigured":false,"decision":"surface_error"

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix is to update the fallback configuration to correctly enable automatic failover when the MiniMax API returns a 529 "overloaded" error.

Guidance

  • Verify that the agents.defaults.fallbacks configuration is correctly set to include the fallback providers (Ollama, Groq) and that the configuration is being properly loaded by OpenClaw.
  • Check the logs for any errors or warnings related to the fallback configuration or the failover process.
  • Investigate why the fallbackConfigured field in the logs is set to false, despite the fallback providers being configured.
  • Review the OpenClaw documentation to ensure that the fallback configuration is correctly formatted and that all required settings are in place.

Example

No code snippet is provided as the issue does not contain sufficient information about the code.

Notes

The issue may be related to a misconfiguration of the fallback providers or an issue with the OpenClaw version being used. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Update the fallback configuration to ensure that it is correctly formatted and that all required settings are in place, and verify that the fallbackConfigured field is set to true in the logs. This should allow OpenClaw to automatically fail over to the configured fallback providers when the MiniMax API returns a 529 "overloaded" error.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Automatic failover after N 529 errors.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: 529 overload errors don't trigger automatic failover to fallback providers [2 pull requests, 1 participants]