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

A 504 means the gateway timed out waiting for the upstream model: the request was sent, but the upstream did not return within the gateway timeout.

504 Gateway Timeout means the gateway gave up waiting for the upstream response. The request was forwarded, but no result came back within the gateway limit. Shortening the output, switching to streaming, or lowering max_tokens usually fixes it.

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 took longer than the gateway timeout allows. The recommended first action is: Switch to streaming output.

Common causes

  • The upstream took longer than the gateway timeout allows
  • A long context pushed inference time up
  • An upstream node is stuck
  • A non-streaming request with a very long output

How to fix

  • Switch to streaming output
  • Shorten the context and lower max_tokens
  • Retry after a short wait
  • Use a model with faster inference

Retry with exponential backoff

The snippet below retries when qwen-plus-character returns 504, 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

Should retries add random jitter?

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. Use exponential backoff for retryable errors and return immediately for the rest.

Can setting max_tokens too high trigger 504?

This is a client-side configuration issue; nothing changes server-side. The capability tags are Tools, and parameter ceilings follow from that capability set. Fail fast on parameter errors instead of spending retries on them.

When qwen-plus-character returns 504, which fields should I read in the response body?

Group the errors by time and node first; the pattern is usually obvious once you do. If it only happens in production, it is usually an environment difference, not the model. This model is served by 阿里巴巴, so upstream status follows the vendor’s own announcements. Log the request ID on every failure — it beats the status code when debugging. Reproduce it once in a staging environment with the same request body.

Does switching to a smaller model reduce 504?

Keep a fallback model ready as well. This model from 阿里巴巴 has several upstream nodes the gateway can switch between. Keep a lighter fallback model ready so the main flow never breaks. Put the model name in config, so switching upstreams needs no code change.

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