> ## 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 140+ 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.

# E1005

> Fork handling — Fork reported on the finalized stream

The pipe reads `/finalized-stream`, where every delivered block is already final, and the portal
answered a request with a fork. The target commits only finalized data and has no rollback path by
design, so the pipe stopped without changing anything it had already written.

**Fix** — [report it](https://github.com/subsquid-labs/pipes-sdk/issues) against the portal. To
restart, rewind (or clear) the target's persisted cursor to a block the portal still considers
canonical — for the Parquet target that is the `_sqd_parquet_state.<pipe-id>.json` file in its
output directory.


## Related topics

- [Error reference](/en/sdk/pipes-sdk/reference/errors.md)