fix(seer): Add timeout recovery for Explorer chat - #122934
Open
gricha wants to merge 2 commits into
Open
Conversation
Use Seer's explicit failure reason to distinguish timeouts from stalled sessions and show a retryable warning without removing the existing stale-session fallback.
gricha
marked this pull request as ready for review
August 27, 2026 21:50
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 23f69a9. Configure here.
NicoHinderling
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

When a response times out, Explorer now shows a warning with Retry instead of leaving the chat in a dead-end error state. Retry resends the latest user message, and New Chat remains available.
getsentry/seer#7911 adds
timeoutandstalledfailure reasons, and #122969 preserves them through Sentry's API boundary. This PR shows the warning only for timeouts and keeps the existing two-minute fallback while those backend changes roll out.The timeout state keeps the composer usable: