[🐴] Recover from initial failed firehose state #4211
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've had some reports of chats failing to update. One possible culprit I've thought of so far is what this PR addresses: if the event bus/firehose is in an error state, starting a new chat will not restart the polling.
So if the user:
It's not clear why the event log is failing yet, but we have had issues with session agents that could cause failures like this, and fixes have been merged already.
What this PR does is handle a dispatched
UpdatePoll
event when the firehose is in an error state, and uses that to basically restart from 0 and attempt a recovery. If it fails again after this, the Convo screen will show its normal error.