-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subgraph instance failed to run: Failed to process trigger in block XXXX #2353
Comments
There appear to be no transactions in the error block on Celo: https://explorer.celo.org/blocks/190080/transactions |
This appears to relate to Epoch rewards on Celo. These appear in |
This has also affected this subgraph |
This likely requires an update to the Celo client so that a transaction is returned for |
@AlexBHarley This is issue happens when the subgraph tries to process an epoch reward event from Celo. Does your subgraph need those events, or would you be happy if the subgraph just skipped over those? |
Do you want to request a feature or report a bug? Report a bug
What is the current behavior? The sub graph stalls at around 1% with the error
Subgraph instance failed to run: Failed to process trigger in block #190080 (ac57ac5a96108b0f133ac6bac59e1bd0df0263d248a4fcc36393464b7c73835d), transaction ac57ac5a96108b0f133ac6bac59e1bd0df0263d248a4fcc36393464b7c73835d: Found no transaction for event, code: SubgraphSyncingFailure, id: QmfBAFQ6JX1QyVG8rfzUYSkax6Lot4j7qaTWdGVZcYWEsL
.If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Here's the link to my Discord message, but concretely here is my bash history.
Here is:
What is the expected behavior? The subgraph builds without error and I can query it.
The text was updated successfully, but these errors were encountered: