You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are the steps to resolve this error? The subgraph indexing process has been running for more than ten days, and deleting the data for re-indexing is not a viable option due to the significant time investment.
Relevant log output
ERRO Trying again after block polling failed: Block data unavailable, block was likely uncled (block hash = 0x4892a7014a6226bf0b3ea8075c242f89155f681771afd141b377da091310ea9e), provider: mainnet-rpc-0, component: EthereumPollingBlockIngestor
IPFS hash
QmdKMmvbh2MW5SopehBANk3YNhHX1fFMjTVGwtQi2zL8hk
Subgraph name or link to explorer
No response
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
None
The text was updated successfully, but these errors were encountered:
Bug report
What are the steps to resolve this error? The subgraph indexing process has been running for more than ten days, and deleting the data for re-indexing is not a viable option due to the significant time investment.
Relevant log output
ERRO Trying again after block polling failed: Block data unavailable, block was likely uncled (block hash = 0x4892a7014a6226bf0b3ea8075c242f89155f681771afd141b377da091310ea9e), provider: mainnet-rpc-0, component: EthereumPollingBlockIngestor
IPFS hash
QmdKMmvbh2MW5SopehBANk3YNhHX1fFMjTVGwtQi2zL8hk
Subgraph name or link to explorer
No response
Some information to help us out
OS information
None
The text was updated successfully, but these errors were encountered: