Docs · error · HTTP 502

-32017 Unknown outcome of a transaction submission

eth_sendRawTransaction / sendTransaction went to exactly one upstream endpoint and no usable answer came back (timeout, connection error or an upstream 4xx/5xx). We never re-send a transaction to another endpoint: it may already sit in a mempool.

What to do

  1. Do not let your SDK auto-retry this 502 — `data.retryable` is false; look it up first with the hash you already hold: `data.lookup` names the method (eth_getTransactionByHash on EVM, getSignatureStatuses on Solana)
  2. Not found after a moment: re-send the identical signed bytes — safe, the nonce protects you
  3. Never re-sign the same nonce with a different payload before that lookup
  4. If it repeats, file the request id as a ticket

Where it lives: /docs/methods.

The exact answer

HTTP 502
{
  "error": {
    "code": -32017,
    "message": "Unknown outcome: eth_sendRawTransaction was submitted to one upstream endpoint and no usable answer came back (Timeout::Error) — it may or may not have been broadcast. Do not auto-retry this answer: look the transaction up (eth_getTransactionByHash) before re-signing; re-sending the identical signed bytes is safe, a new signature with the same nonce is not.",
    "data": {
      "request_id": "<uuid>",
      "support": "/support/new?request_id=<uuid>",
      "attempts": 1,
      "cause": "Timeout::Error",
      "never_retried": true,
      "retryable": false,
      "lookup": "eth_getTransactionByHash",
      "decoder": "https://flexyield.io/docs/errors/-32017"
    }
  }
}

All codes: error decoder · methods and limits · file it: /support/new?request_id=….