The autofix docs mention that an issue must have "a sufficient fixability score" to trigger automation, but don't specify what "sufficient" means in practice.
The source code uses a MEDIUM fixability score as the minimum threshold to gate automation — issues scoring below MEDIUM are skipped entirely (unless the issue type always triggers automation). This detail is missing from the docs.
Suggested additions:
- Clarify that MEDIUM is the baseline fixability threshold for automation eligibility in the "When Autofix Runs Automatically" section
- Note that
issue.seer_actionability (a filter available in the Issues view) maps to these fixability tiers: super_low, low, medium, high, super_high
- Optionally explain how the
autofix_automation_tuning project setting maps actionability tiers to the minimum score required, i.e. a stricter tuning setting requires a higher fixability score before automation runs
Reference: src/sentry/seer/autofix/trigger.py in getsentry/sentry.
Action taken on behalf of Simon Zhong.
The autofix docs mention that an issue must have "a sufficient fixability score" to trigger automation, but don't specify what "sufficient" means in practice.
The source code uses a MEDIUM fixability score as the minimum threshold to gate automation — issues scoring below MEDIUM are skipped entirely (unless the issue type always triggers automation). This detail is missing from the docs.
Suggested additions:
issue.seer_actionability(a filter available in the Issues view) maps to these fixability tiers:super_low,low,medium,high,super_highautofix_automation_tuningproject setting maps actionability tiers to the minimum score required, i.e. a stricter tuning setting requires a higher fixability score before automation runsReference:
src/sentry/seer/autofix/trigger.pyingetsentry/sentry.Action taken on behalf of Simon Zhong.