Documentation · Reference
Troubleshooting
Start with the HTTP status and the error code. Each one below says what it means and what to do next.
Find your error
Errors have error.message, type, param and code. param names the field, or is null. Some errors include details. Read Retry-After before sending again.
| Status | Code or type | Meaning |
|---|---|---|
| 400 | invalid_json, unknown_parameter, unsupported_parameter, unsupported_value, invalid_type, invalid_value, missing_required_parameter, conflicting_parameters, unsupported_combination | Invalid request. The field path is in param. |
| 400 | invalid_message_order, unsupported_content_type, unsupported_tool_type, invalid_tool_schema, invalid_response_format | Unsupported message, content, tool or schema. |
| 400 | context_length_exceeded, completion_limit_exceeded, max_tokens_too_small_for_reasoning | The input does not fit, an output allowance is refused, or thinking has fewer than 256 output tokens. Oversized output is normally clamped. |
| 401 | missing_api_key, invalid_api_key | Missing, disabled or invalid credentials. |
| 402 | insufficient_quota | Available balance cannot cover the reservation. details may include required_reservation_micro_usd. |
| 403 | client_account_required | This route requires a client account. |
| 404 | model_not_found, result_not_found, job_not_found, unsupported_endpoint, unknown_endpoint | Model, result, job or endpoint not found. |
| 405 | method_not_allowed | Use a method from Allow. |
| 408 | request_timeout | Reading the request body timed out. |
| 409 | idempotency_conflict | The key was used for different input. |
| 413 | request_too_large | Request exceeds the input byte bound. |
| 422 | request_output_limit | A paid request hit its output cap before a required result. usage and billing describe the charge. A stream carries this as an error event, then [DONE]. Fetching the result returns 422 again. |
| 429 | concurrent_job_limit, concurrent_reasoning_limit | Another account job or heavy thinking job is active. Retry-After is 1 or 5 seconds respectively. The account job limit is checked first. |
| 429 | server_busy | The server is at its limit of running requests. Nothing was started or charged. Retry-After is 5 seconds. |
| 429 | rate_limit_error | Request limiter. Wait for Retry-After. |
| 503 | capacity_queue_expired, payment_unavailable, no_node_available, service_draining, stream_unavailable | Capacity, payment readiness, maintenance or service failure. Retry-After is 1 for capacity_queue_expired, 5 for payment_unavailable and no_node_available, and 15 for service_draining. stream_unavailable has no default retry delay. |
| 503 | no_node_available | No node that can serve the model is online, so the request did not reach a node. Wait for the Retry-After seconds. |
If a request fails on a node before any output is sent, Tenvor may retry it once on another node, if one is free. You are not charged for the attempt that failed. A retry is invisible to you. The request keeps its id, a stream carries on under that id, and you get one result and one receipt. Nothing in the response says a retry happened.
A retry is not a promise
A retry is not a promise that the request completes. It takes extra time, and it needs a second node that is free soon. A request is retried at most once, and never after you cancel it.
After admission, inference_failed is an error event. stream_interrupted means delivery was interrupted and can follow a charged completion. Fetch the stored result before deciding what happened. Neither a generic 503 nor a broken connection proves no charge.
A reply that never arrived, or stopped half way
Prefer streaming for long replies. A broken connection does not prove failure or no charge. Fetch the stored result with X-Request-Id or the same Idempotency-Key. inference_failed is a failed job; request_output_limit carries a charge. stream_interrupted may follow a charged completion.
- A stream ended with an error event. If the node failed before any output was sent, the retry was not possible or failed too.
- A reply took longer than usual. If a request fails on a node before any output is sent, Tenvor may retry it once on another node, if one is free. That takes extra time, and nothing in the response says it happened.
Report a problem
Write to support@tenvor.io with these and nothing else:
- The time, to the nearest few minutes, and your time zone.
- The client and its version, or the SDK.
- The HTTP status and the error code.
- Whether the Usage page shows a charge for it.
- What you expected, and what happened.
Leave these out
Your API key, the prompt, the reply, tool arguments, files, and screenshots that show any of them. If a person at Tenvor needs the X-Request-Id, they will ask for it.
The same list is in the plain-text checklist, for pasting into an email.
Content checked . Live limits and prices can change.