Skip to content
向量潮汐 / Vectide

VECTIDE · Practical documentation

Troubleshoot authentication, limits and interruptions

Preserve the error and identify the failing layer before retrying.

Updated 14 October 2026 · Maintained by Vectide

Read more than the HTTP status: check the error body, request ID, model entitlement, dashboard allowance and stream completion.

Narrow down the cause

SymptomFirst checksNext step
401 / 403Whitespace, expired key, account and model accessRecheck settings without logging the key.
404 / model not foundBase URL, endpoint path and exact model IDCompare with the quickstart request.
429Error body, allowance windows, concurrency and upstream limitsFollow dashboard timing or Retry-After when supplied; distinguish exhausted quota from transient pressure.
5xx / timeoutRequest ID, time, upstream error, network and client timeoutUse bounded retries and record each outcome and deduction.
HTTP 200 with a truncated answerStream errors, termination events, disconnects and timeoutsInspect the full event sequence, not status alone.

Retries and model switching

Use bounded backoff for recoverable network or transient service failures. Fix authentication and entitlement errors before retrying, and wait for exhausted allowances to reset. A timeout does not necessarily mean processing never happened; inspect usage before resending a batch.

Before switching, confirm the alternative model is included in your account. A different model or a larger plan does not guarantee resolution of an upstream issue.

What to include in a support request

  • Time and timezone, client name and version.
  • Model ID, endpoint path and whether streaming was enabled.
  • Status, error body and request ID, with keys and private content removed.
  • Dashboard allowance state and whether a minimal independent request reproduces the error.

Contact Vectide support

References and service information: CodingPlan plans TokenPlan Full guide

Continue with