feat(flags): Remove graduated issue_detection feature flags#108775
Merged
feat(flags): Remove graduated issue_detection feature flags#108775
Conversation
github-actions
bot
added
Scope: Frontend
Contributor
|
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
ceorourke
reviewed
Feb 21, 2026
ceorourke
approved these changes
Feb 23, 2026
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
src/sentry/workflow_engine/endpoints/organization_detector_anomaly_data.py
Show resolved
Hide resolved
Remove flags that have been enabled at 100% via flagpole with no conditions: - organizations:anomaly-detection-threshold-data - organizations:issue-detection-sort-spans - organizations:large-http-payload-detector-improvements - organizations:suspect-commits-in-emails These flags have been fully rolled out and are safe to remove. Their behavior is now the default for all organizations.
After removing the anomaly-detection-threshold-data feature flag,
the anomaly data endpoint is now called whenever dynamic detection
is active. Tests that switch to or load dynamic detection need a
mock for the /detectors/{id}/anomaly-data/ endpoint.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The test fixture had two spans sharing the same span_id. After removing the issue-detection-sort-spans feature flag (making span tree sorting unconditional), build_tree deduplicates by span_id, causing one span to be lost. Give the second span a unique ID and update the test expectation to reflect the now-correct evidence_display. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
wedamija
force-pushed
the
flag-burner/ga/issue-detection
branch
from
e368746 to
e46dfd2
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Removes 4 feature flags owned by the issue_detection team that have been enabled at 100% via flagpole with no conditions for an extended period:
organizations:anomaly-detection-threshold-data— Anomaly detection threshold data endpointorganizations:issue-detection-sort-spans— Sorting spans for issue detectionorganizations:large-http-payload-detector-improvements— Large HTTP payload detector improvements (path filtering)organizations:suspect-commits-in-emails— Suspect commit information in workflow notification emailsThese flags have been fully rolled out and their behavior is now the default. Owners should consider self-hosted implications — these features will now be available to all self-hosted users as well.
Changes:
temporary.pyfeatures.has()checks, keeping the enabled code paths@with_featuretest decorators and feature-flag-disabled test casesTest plan