LOG_RANGE_TOO_LARGE
What LOG_RANGE_TOO_LARGE means, why NetworkError throws it, what to show users and how to fix it in ensforge. Also covers retry safety.
NetworkErrorRetryable
@ensforge/sdk
What happened
The RPC provider's eth_getLogs limits make this block range too expensive.
What to show users
| Title | Message | Action |
|---|---|---|
| History unavailable | This RPC provider cannot return events for such a long period. |
How to fix
Narrow the block range, use an RPC URL with wider log ranges, or use the indexer for history.
Retry safety
Retrying the same call can succeed (retryable: true).
Actions that throw it
| Action | When |
|---|---|
event.get | when the provider's log limits make the range too expensive. |
Any action can fail with NetworkError: it is part of Errors.CommonError.
Catch it
Errors.hasCode("LOG_RANGE_TOO_LARGE") narrows to this error. See Handle errors.
Was this page helpful?