Error 429: what to do when glm-5.2 fails
A 429 means you hit a rate limit: the number of requests or tokens sent within a time window exceeded your plan quota.
429 Too Many Requests is a rate-limit response, not an error. It means the request itself is valid but exceeded the request rate or concurrency allowed by your current plan. Back off and retry within the window indicated by the response headers; the request body does not need to change.
glm-5.2 is served by Z.AI. 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: Too many concurrent requests. The recommended first action is: Limit concurrency and retry with exponential backoff.
Common causes
- Too many concurrent requests
- Quota of the current plan exhausted
- Retrying immediately without backoff
How to fix
- Limit concurrency and retry with exponential backoff
- Switch to a plan with a larger quota
- Cache repeated requests
Retry with exponential backoff
The snippet below retries when glm-5.2 returns 429, 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 = 'glm-5.2'
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 endpoint | https://api.airai.cc/v1 |
|---|---|
| OpenAI-compatible | OpenAI-compatible |
| Vendor | Z.AI |
|---|---|
| Context | 1M |
| Capabilities | Reasoning, Tools, Open Weights |
| API formats | openai, openai-response, openai-response-compact, anthropic, gemini, openai-alpha-search |
| Billing formula | p * 1.4 + cr * 0.26 + cc * 0 + c * 4.4 |
FAQ
Is 429 related to the capability of the model itself?
This error is unrelated to model capability; it is a gateway-layer issue. It is usually transient and recovers on its own. The capability tags for this model are Reasoning, Tools, Open Weights. 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.
How should I schedule batch jobs when glm-5.2 returns 429?
Concurrency and timeouts are the real variables here, not the model itself. Lower the concurrency first — most throughput complaints disappear once you do. This model has a 1M context window and comes from Z.AI. Start with low concurrency, watch it for a few minutes, then scale up. Add a cache layer so repeated requests do not all hit the model.
Can switching to a comparable model from another vendor fix 429?
Keep a fallback model ready as well. Building a fallback into the architecture is more reliable than patching errors one by one. This model from Z.AI has several upstream nodes the gateway can switch between. Put the model name in config, so switching upstreams needs no code change.
Should retries add random jitter?
You usually do not need to change business code, just the call cadence. With billing p * 1.4 + cr * 0.26 + cc * 0 + c * 4.4, failed requests are not counted toward usage. Set the retry ceiling to 3–5 attempts and add jitter.
Other errors on this model
- glm-5.2: error timeout — causes and fixes
- glm-5.2: error 500 — causes and fixes
- glm-5.2: error 502 — causes and fixes
- glm-5.2: error 503 — causes and fixes
- glm-5.2: error 504 — causes and fixes
- glm-5.2: error 401 — causes and fixes
- glm-5.2: error 403 — causes and fixes
- glm-5.2: error 400 — causes and fixes
Other models with the same error
- gpt-5
- claude-opus-5
- gemini-2.5-pro
- deepseek-v4-pro
- grok-4.3
- llama-3.3-70b-instruct
- qvq-max
- qwq-32b
- glm-5
- MiniMax-M3
- kimi-k3
- hy3
- doubao-seed-evolving
- mimo-v2.5
- gpt-4o
- claude-opus-4-6
Data updated: 2026-10-10 12:10