Error 503: what to do when qwen-plus-character fails

A 503 means the service is temporarily unavailable, usually due to maintenance or overload. Unlike 429, it is not about your quota — it is a capacity problem on the server side.

503 Service Unavailable means the service cannot handle the request right now, usually from overload or maintenance. The distinction from 429 matters: 429 means your quota is used up, 503 means server capacity is short. Increase the backoff interval rather than swapping keys.

qwen-plus-character is served by 阿里巴巴. Everything on this page — triggers, fixes and measured data — is compiled from the real runtime behaviour of this model at the gateway layer.

At this gateway, the most common trigger is: The upstream model is overloaded. The recommended first action is: Retry later with a longer backoff.

Common causes

  • The upstream model is overloaded
  • The service is under maintenance or rolling out
  • The node in your region is unavailable
  • A sudden traffic spike

How to fix

  • Retry later with a longer backoff
  • Switch to a less loaded equivalent model
  • Avoid batch jobs during peak hours
  • Watch our announcements

Retry with exponential backoff

The snippet below retries when qwen-plus-character returns 503, up to 5 attempts, with an increasing wait plus random jitter so concurrent calls do not retry in lockstep. Read the base URL and API key from environment variables — never hardcode them.

import os, time, random
import requests

BASE  = os.getenv("OPENAI_BASE_URL")   # e.g. https://<your-gateway>/v1
KEY   = os.getenv("OPENAI_API_KEY")
MODEL = 'qwen-plus-character'


def chat(messages, retries=5):
    """Retry with exponential backoff + jitter."""
    for i in range(retries):
        try:
            r = requests.post(
                BASE + "/chat/completions",
                headers={"Authorization": "Bearer " + KEY},
                json={"model": MODEL, "messages": messages, "stream": True},
                timeout=60,
            )
            if r.status_code == 429 or r.status_code >= 500:
                time.sleep(min(2 ** i + random.uniform(0, 1), 30))
                continue
            r.raise_for_status()
            return r.json()
        except requests.exceptions.Timeout:
            time.sleep(min(2 ** i + random.uniform(0, 1), 30))
    raise RuntimeError("gave up after " + str(retries) + " retries")


print(chat([{"role": "user", "content": "hello"}]))

Key facts for this model

API endpointhttps://api.airai.cc/v1
OpenAI-compatibleOpenAI-compatible
Vendor阿里巴巴
Context32.8K
CapabilitiesTools
API formatsopenai, openai-response, openai-response-compact, anthropic, gemini, openai-alpha-search
Billing formulap * 0.115 + c * 0.287

FAQ

Will I be charged when qwen-plus-character returns 503?

No charge — only output actually produced counts toward usage. Billing follows p * 0.115 + c * 0.287, so no output means no charge. When estimating cost from p * 0.115 + c * 0.287, include the retry budget.

Is 503 on qwen-plus-character related to my account quota?

Raising the plan ceiling or lowering the call rate both help. Billing follows p * 0.115 + c * 0.287, so no output means no charge. Check your balance and rate limits in the console before debugging code.

Which status codes are worth retrying, and which never help?

You usually do not need to change business code, just the call cadence. Retrying is the most effective first step. With billing p * 0.115 + c * 0.287, failed requests are not counted toward usage. Set the retry ceiling to 3–5 attempts and add jitter. Use exponential backoff for retryable errors and return immediately for the rest.

503 keeps recurring on qwen-plus-character — how do I tell whether it is the model or my account?

This error is unrelated to model capability; it is a gateway-layer issue. The capability tags for this model are Tools. If it persists for several minutes, contact platform support to confirm upstream status. Decide account-level versus model-level first; the two need completely different handling.

Other errors on this model

Other models with the same error

Back to the model page

Data updated: 2026-10-10 18:35

Technical SupportLive Support
Back to Top