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
In V2, we don't make a distinction between historical real-time executions, therefore causing the historical block height to be written to the real-time column. This can be observed via the "Indexer State" UI:
As the Indexer starts:
A few moments later once the historical process starts, note that the "Current Block Height" is less than the above:
We need to update the Runner so that it sets the 'historical' flag when executing historical blocks.
The text was updated successfully, but these errors were encountered:
In V2, we don't make a distinction between historical real-time executions, therefore causing the historical block height to be written to the real-time column. This can be observed via the "Indexer State" UI:
As the Indexer starts:
A few moments later once the historical process starts, note that the "Current Block Height" is less than the above:
We need to update the Runner so that it sets the 'historical' flag when executing historical blocks.
The text was updated successfully, but these errors were encountered: