Billing & Support
Contact Technical Support
Prepare reproducible, redacted evidence so support can diagnose API problems quickly.
A good report lets support locate an individual request, understand its impact, and reproduce the issue without exposing keys or user data.
Prepare before submitting
| Information | Example | Notes |
|---|---|---|
| Time | 2026-09-22 14:30:18 UTC+8 | Always include the time zone. |
| Request ID | chatcmpl-… | Provide the complete request identifier, not an API key. |
| Endpoint and model | POST /v1/chat/completions, qwen-turbo | State whether the request was streaming. |
| Error | HTTP status and complete error object | Remove keys and sensitive business data. |
| Impact | All requests / one model / one region | Include approximate failure rate and start time. |
| Runtime | Python 3.12 and installed openai SDK version | Minimal runnable code helps. |
Report template
Title: qwen-turbo streaming requests consistently return 504
Time and time zone:
Impact:
Endpoint and model:
Streaming:
HTTP status:
Request ID:
SDK language and version:
Consistently reproducible:
Troubleshooting attempted:
Redacted minimal request:
Redacted error response:Do not submit
- Full API keys, passwords, cookies, or other credentials.
- Unredacted personal information, customer data, or internal secrets.
- Reports that only say the API is broken without time, model, or errors.
- Project archives that cannot run and contain extensive unrelated business code.
Urgent incidents
- Preserve request IDs and error samples; check whether only certain models are affected.
- Reduce non-critical traffic to protect essential requests and account balance.
- Degrade or queue according to a validated business policy.
- Report the impact clearly and keep support updated with new evidence.