RPC error -32005 / -32000: query returned more than N results

Last updated: September 16, 2026

At a glance

Cause

Public nodes cap how many log entries a single eth_getLogs may return, and report the overflow either as -32005 or as -32000 with the same wording. The number in the message is the serving node's threshold and differs between sources, so a client that hard-codes one value will be wrong somewhere. On Robinhood Chain the log planner treats this answer as an instruction to split the block range and re-query, rather than failing the call.

Solution

1. Halve the block range and retry, repeating until the window fits — this is what our Robinhood log planner does internally.
2. Narrow the filter itself: a specific address and topic set usually shrinks the result far more than a smaller range.
3. Read the number out of the message rather than assuming a constant; nodes publish different ceilings.
4. For whole-block work, eth_getBlockReceipts returns a block's receipts in one call instead of a wide log query.

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32005,
    "message": "query returned more than 1000 results"
  }
}