chore(flags): Remove organizations:sdk-crash-detection feature flag#111267
Closed
wedamija wants to merge 1 commit into
Closed
chore(flags): Remove organizations:sdk-crash-detection feature flag#111267wedamija wants to merge 1 commit into
wedamija wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
Scope: Backend
cvxluo
reviewed
Mar 21, 2026
Contributor
cvxluo
left a comment
cvxluo
left a comment
There was a problem hiding this comment.
this PR seems to have turned it off intentionally in de: https://github.com/getsentry/sentry-options-automator/pull/6243
there's also a reference to the flag here:
Member
Author
Ahh, damn... It'd be nice to migrate this to use options automator instead |
SDK crash detection is fully rolled out in US and s4s2 (ga-rollout: 1.0) but was never enabled in DE (ga-rollout: 0.0), which appears to be an oversight. Rather than enabling it region-by-region, graduate the flag entirely so all regions get SDK crash detection. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
wedamija
force-pushed
the
danf/remove-sdk-crash-detection-flag
branch
from
2c651b2 to
61104d5
Compare
scttcper
approved these changes
Mar 25, 2026
wedamija
added a commit
that referenced
this pull request
Apr 1, 2026
This flag is still in use, but using an old deprecated rollout handler that I'd like to remove. Setting this to flagpole allows us to still fall back to the old handler until we roll out the options in `sentry-options-automator` and remove the old handler. Relatd to #111267, which I'll likely close
wedamija
added a commit
that referenced
this pull request
Apr 2, 2026
…112069) This flag is still in use, but using an old deprecated rollout handler that I'd like to remove. Setting this to flagpole allows us to still fall back to the old handler until we roll out the options in `sentry-options-automator` and remove the old handler. Related to #111267, which I'll likely close
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.
3 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
organizations:sdk-crash-detectionfeature flag gate frompost_process.pytemporary.pyWhy
SDK crash detection is controlled by an option-backed rollout handler in getsentry with three rollout options (
la-rollout,ea-rollout,ga-rollout). Currently:ga-rollout: 1.0(fully enabled)ga-rollout: 1.0(fully enabled)ga-rollout: 0.0(disabled — appears to be an oversight)Rather than enabling DE separately, we're graduating the flag entirely so SDK crash detection runs everywhere. The option-backed rollout handler and LA org list in getsentry will be cleaned up in a follow-up PR after this deploys.
Merge order
ROLLOUT_FEATURESentry,SDK_CRASH_DETECTION_LA_ORGScc @getsentry/ingest @getsentry/issue-detection-backend
🤖 Generated with Claude Code