Currently using MiniMax M2.7 as primary with blockrun/eco as fallback. When MiniMax returns HTTP 500 with error insufficient balance (1008) (hourly cap hit or balance exhausted), the fallback does not activate. Instead: 2. Each retry fails with same billing error 4. Error propagates to user Billing/balance errors (HTTP 500 with insufficient balance, quota exceeded, resource exhausted, error code 1008) should trigger the configured fallback model, just like rate-limit errors (429) do.

• Error: HTTP 500, code 1008, message "insufficient balance" None available - the fallback simply does not activate on these error types.

Fix Plan

To fix the issue, we need to modify the OpenClaw configuration to treat billing/balance errors the same as rate-limit errors for fallback purposes.

• Update the OpenClaw configuration to include billing/balance error codes in the retry mechanism:

# OpenClaw configuration update
retry_on_errors = [
    'rate_limit', 
    'quota', 
    'resource_exhausted', 
    '429', 
    '1008',  # insufficient balance
    'insufficient balance', 
    'quota exceeded'
]

• Ensure the fallback model is correctly configured:

# Fallback model configuration
primary_model = 'minimax-portal/MiniMax-M2.7'
fallback_model = 'blockrun/eco'

• Implement a custom error handler to catch and handle billing/balance errors:

# Custom error handler
def handle_billing_error(error):
    if error.code == 1008 or error.message in ['insufficient balance', 'quota exceeded']:
        # Trigger fallback model
        return fallback_model
    else:
        # Handle other errors
        return None

Verification

To verify the fix, test the following scenarios:

• Primary model returns HTTP 500 with error code 1008 (insufficient balance)
• Primary model returns HTTP 500 with error message quota exceeded
• Primary model returns HTTP 429 (rate-limit error)

In each scenario, verify that the fallback model is triggered and the request is successfully processed.

Extra Tips

• Monitor the error rates and adjust the retry mechanism as needed to prevent abuse.
• Consider implementing a notification system to alert administrators when the primary model returns billing/balance errors.
• Review the OpenClaw documentation for any updates on handling billing/balance errors.