fix(night-shift): Remove poll timeout that aborted Explorer runs#113137
Merged
fix(night-shift): Remove poll timeout that aborted Explorer runs#113137
Conversation
The polling loop in agentic triage raised a TimeoutError after 120s, which abandoned the entire night shift run for an org even though the Explorer was still working on the Seer side. For large orgs like Sentry the Explorer can take longer than 120s to investigate all candidates. Remove the client-side poll timeout and let the task's own processing deadline (5 minutes) be the backstop instead. Fixes SENTRY-5NFV Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Backend
JoshFerge
approved these changes
Apr 15, 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
2 participants
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.
The polling loop in
_poll_with_loggingraised aTimeoutErrorafter 120s, which caused the entire night shift run to be abandoned for an org — even though the Explorer was still actively working on the Seer side. For large orgs like Sentry (70 eligible projects, 10 candidates), the Explorer can legitimately need more than 120s to investigate all candidates.In the observed incident (SENTRY-5NFV), the Explorer had finished analyzing all issues and was writing its final verdicts when the timeout killed the run at 121.3s.
This removes the client-side poll timeout entirely. The task's own
processing_deadline_duration(5 minutes) serves as the backstop. There's no cancel API on the Explorer client, so a client-side timeout only wastes the Seer-side work that continues running regardless.Fixes SENTRY-5NFV