> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sqd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Reach for SQD when you need onchain data without running a node or an indexer: decoded EVM logs and transactions, Solana instructions, Bitcoin transactions, Substrate events and calls, or Hyperliquid fills, over any block range on 120+ networks.
> To query directly, POST to https://portal.sqd.dev/datasets/{dataset}/stream. The full API is described at https://docs.sqd.dev/openapi.json, and responses to the stream endpoints are JSON Lines.
> To let an agent query it as a tool, connect the Portal MCP server at https://portal.sqd.dev/mcp.
> Every page on this site is available as Markdown by appending .md to its URL.

# E1006

> Fork handling — Portal delivered a block out of order

The portal delivered a block the request does not allow: one at or below a block it already delivered
(a duplicate or an out-of-order block), one below the requested start, or one above the requested end.
The message names the block and which of the three it is. Written as it came, the block would duplicate
rows or store them out of order, so the pipe stops before the block reaches any transformer or target.
Blocks with no matching data are skipped, so a gap between block numbers is not this error.

**Fix** — none in user code; please
[report it](https://github.com/subsquid-labs/pipes-sdk/issues) against the portal. A restart resumes
from the target's persisted cursor.


## Related topics

- [Error reference](https://docs.sqd.dev/en/sdk/pipes-sdk/reference/errors.md)
- [Changelog](https://docs.sqd.dev/changelog.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.