Skip to content

[Bug] Subgraph hit error: internal constraint violated: Batches must go forward. Can't append a batch with block pointer... #4770

Closed as not planned

Description

@brianluong

Bug report

Subgraph failed after hitting this error:
Jul 14 00:13:20.858 ERRO Subgraph failed with non-deterministic error: Failed to transact block operations: internal constraint violated: Batches must go forward. Can't append a batch with block pointer #6265702 (c2d228257112989474262df4754e5bceae3932c36094aa32feb07c69da390797) to one with block pointer #6265702 (c2d228257112989474262df4754e5bceae3932c36094aa32feb07c69da390797), retry_delay_s: 213, attempt: 1, sgd: 365, component: SubgraphInstanceManager

The subgraph started syncing after restarting graph-node.

What caused this error and how can we avoid it in the future?

Some information to help us out

  • Tick this box if this bug is caused by a regression found in the latest release.
  • Tick this box if this bug is specific to the hosted service.
  • I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux

Activity

  1. azf20 commented on Aug 9, 2023

    @azf20
    Contributor

    hey @brianluong did you do anything around the time this happened (e.g. pausing or reassigning the subgraph), or did this just happen spontaneously?
    cc @lutter as this is batching related

  2. brianluong commented on Aug 9, 2023

    @brianluong
    Author

    @azf20 It seemed to happen spontaneously.

  3. github-actions commented on Feb 6, 2024

    @github-actions

    Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.

  4. dimitrovmaksim commented on Oct 21, 2026

    @dimitrovmaksim
    Collaborator

    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! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    StalebugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions