Stored cursor ignored on reboot #12
Description
Describe the bug
The feed keeps track of a timestamp as a cursor used when connecting to the Jetstream API. If the feed experiences a fatal error, it reboots but then fails to restart consumption of the jetstream where it left off. Appears to start indexing the jetstream feed 2 days in the past.
Expected behavior
On reboot, the feed should:
- Query the state of the cursor and fetch the timestamp if it exists
- Start the connection to the Jetstream using the cursor as a query parameter
- Indexing of the Jetstream feed should start from where the feed indexer left off.
Additional context
A short term patch would be to ignore the cursor in the database and restart the feed from the current timestamp minus ~1 hour or some other standard unit of time.