Repository navigation
diffEntitiesAtBlock in the index-node API fails for immutable entities #4433
Description
In a subgraph that uses immutable entities, the following query fails:
{
entityChangesInBlock(subgraphId: "<some id>", blockNumber: 1234){
updates {
entities
type
}
deletions {
entities
type
}
}
}
The error is
{
"errors": [
{
"message": "Store error: store error: column \"block_range\" does not exist"
}
]
}
Activity
github-actions commentedon Sep 12, 2023
Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.
github-actions commentedon Mar 11, 2024
Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.
madumas commentedon Jul 23, 2026
Still relevant, and still reproducing today: we hit exactly this error on deployments with immutable entities (graph-node 0.42.1 on our side, and the same error on third-party indexers running 0.36.0 through 0.44.0 — so it is not version- or configuration-specific).
It would be genuinely useful to have this fixed:
entityChangesInBlockis the cheapest way for an indexer to localise a POI divergence, and it is unavailable on every deployment using immutable entities.dimitrovmaksim commentedon Oct 21, 2026
Hi!
We're refreshing the graph-node issue backlog to help focus on current priorities and make it easier to track and address relevant issues. As part of this cleanup, we're closing issues created in 2025 or earlier.
If this issue is still relevant, please open a new issue (linking back to this one) or leave a comment here with any updated context and tag @dimitrovmaksim, so we can reassess and prioritize it.
Thank you for your contributions to graph-node! 🙏