diegosouzapw/OmniRoute · error

PROXY_002

PROXY_002

Error message

Proxy timeout

What it means

Error "Proxy timeout" thrown in diegosouzapw/OmniRoute.

Source

Thrown at src/shared/constants/errorCodes.ts:64

    message: "No credentials for provider",
    httpStatus: 400,
    category: "AUTH",
  },
  AUTH_007: {
    code: "AUTH_007",
    message: "Session expired (re-login required)",
    httpStatus: 401,
    category: "AUTH",
  },

  // ── Proxy ──
  PROXY_001: {
    code: "PROXY_001",
    message: "Proxy connection failed",
    httpStatus: 502,
    category: "PROXY",
  },
  PROXY_002: { code: "PROXY_002", message: "Proxy timeout", httpStatus: 504, category: "PROXY" },
  PROXY_003: {
    code: "PROXY_003",
    message: "All proxies exhausted",
    httpStatus: 503,
    category: "PROXY",
  },

  // ── Rate Limiting ──
  RATE_001: {
    code: "RATE_001",
    message: "Rate limit exceeded",
    httpStatus: 429,
    category: "RATE_LIMIT",
  },
  RATE_002: {
    code: "RATE_002",
    message: "Daily budget exceeded",
    httpStatus: 429,

View on GitHub (pinned to a179ffed5b)

When it happens

Trigger: Thrown at src/shared/constants/errorCodes.ts:64 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

• Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

AI-assisted analysis of diegosouzapw/OmniRoute@a179ffed5b (2026-08-25). Data as JSON: /api/errors/8dea926cbeeca823. Report an issue: GitHub.