Error 504: what to do when qwen-turbo 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-turbo is served by Alibaba. 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-turbo 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-turbo'


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
VendorAlibaba
Context1M
CapabilitiesReasoning, Tools
API formatsopenai, openai-response, openai-response-compact, anthropic, gemini, openai-alpha-search
Billing formulap * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2

FAQ

Is 504 on qwen-turbo related to my account quota?

It is mainly a quota matter, not a fault in the model itself. Raising the plan ceiling or lowering the call rate both help. With billing p * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2, failed requests are not counted toward usage. Check your balance and rate limits in the console before debugging code.

Does switching to streaming reduce 504?

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

How long should the retry interval be when qwen-turbo returns 504?

You usually do not need to change business code, just the call cadence. With billing p * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2, 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.

Should I fall back to a backup model when 504 appears?

Building a fallback into the architecture is more reliable than patching errors one by one. This model from Alibaba has several upstream nodes the gateway can switch between. Keep a lighter fallback model ready so the main flow never breaks.

Other errors on this model

Other models with the same error

Back to the model page

Data updated: 2026-10-11 15:15

Technical SupportLive Support
Back to Top