From 867eb923c08e3eb71c69e80650cbb0d0632811b6 Mon Sep 17 00:00:00 2001 From: Junior Date: Wed, 6 May 2026 14:48:30 +0000 Subject: [PATCH 1/2] docs(autofix): clarify when Autofix runs automatically Replace the confusing single sentence about 'highly actionable' and 'high medium or above fixability score' with a structured section that explains: - The four requirements for automatic triggering - What the fixability score is and how it's computed - The score tiers and what each one unlocks - How the user-configurable stopping point caps automation depth --- .../ai-in-sentry/seer/autofix/index.mdx | 34 +++++++++++++++++-- 1 file changed, 32 insertions(+), 2 deletions(-) diff --git a/docs/product/ai-in-sentry/seer/autofix/index.mdx b/docs/product/ai-in-sentry/seer/autofix/index.mdx index 1b961c856b7955..284eba963033e4 100644 --- a/docs/product/ai-in-sentry/seer/autofix/index.mdx +++ b/docs/product/ai-in-sentry/seer/autofix/index.mdx @@ -40,10 +40,40 @@ Seer's Issue Autofix flow follows a three step process: 2. [Solution Identification](#solution-identification): Identify a solution based on the analysis 3. [Code Generation](#code-generation): Generate a code fix and (optionally) open a PR, or hand off to a coding agent -You can always manually trigger the Autofix flow from the Issue Details page. Issues will automatically trigger the flow when an agent is configured for background handoff and the Issue is highly actionable with 10+ events captured and high medium or above fixability score. +You can always manually trigger the Autofix flow from the Issue Details page. + +### When Autofix Runs Automatically + +When automation is enabled in your project's Seer settings, Sentry can also trigger Autofix automatically on new issues that meet the following criteria: + +1. **Autofix automation is enabled** — The automation toggle in your project's Seer settings must be turned on. +2. **The issue has 10 or more events** — Sentry waits until the issue has captured at least 10 events to ensure it's worth investigating. +3. **The issue occurred within the last 14 days** — Only recent issues are eligible for automatic runs. +4. **The issue has a sufficient fixability score** — Sentry's ML model must estimate the issue is reasonably fixable (see below). + +#### Fixability Score + +When Seer evaluates an issue, it assigns a **fixability score** — a value between 0 and 1 that estimates how straightforward the issue is to resolve. This score is generated by a machine-learning model that analyzes the issue summary and classifies it on a spectrum from "complex and very difficult to resolve" to "simple and easily resolved." + +The fixability score determines **whether** Autofix runs automatically, and **how far** it goes: + +- **Below 0.40 (Low)** — The issue is not considered fixable enough for automation. Autofix will not run automatically, but you can still trigger it manually. +- **0.40 – 0.66 (Medium)** — Autofix runs automatically but stops at **root cause analysis**. Sentry identifies the likely cause and presents it for your review. +- **0.66 – 0.78 (High)** — Autofix runs automatically through **code changes**. Sentry identifies the root cause and suggests a fix. +- **0.78 and above (Very High)** — Autofix runs automatically and can **open a pull request** with the suggested fix. + +#### Capping Automation Depth + +Even when the fixability score suggests a deeper level of automation, you can set a maximum stopping point in your project's Seer settings. The available options are: + +- **Root cause analysis only** — Autofix identifies the cause but doesn't suggest code changes. +- **Code changes** — Autofix suggests a fix but doesn't open a PR. +- **Open a pull request** — Autofix can go all the way to opening a PR (default). + +Your chosen stopping point acts as an upper bound — Autofix will never go further than what you allow, regardless of the fixability score. -If you've recently set up Seer, existing issues will need Autofix to be run manually. +If you've recently set up Seer, existing issues will need Autofix to be run manually. ### Root Cause Analysis From 7e38f84049d6e74c0ed7276a60cd7e94ac8d1d44 Mon Sep 17 00:00:00 2001 From: Rahul Chhabria Date: Wed, 6 May 2026 09:38:13 -0700 Subject: [PATCH 2/2] docs(autofix): remove redundant criterion and clarify wording MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Address review bot feedback: - Remove "Autofix automation is enabled" bullet — already stated as a prerequisite in the introductory sentence. - Change "new issues" to "issues" to align with the 14-day recency filter. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/product/ai-in-sentry/seer/autofix/index.mdx | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/product/ai-in-sentry/seer/autofix/index.mdx b/docs/product/ai-in-sentry/seer/autofix/index.mdx index 284eba963033e4..cd980930fed231 100644 --- a/docs/product/ai-in-sentry/seer/autofix/index.mdx +++ b/docs/product/ai-in-sentry/seer/autofix/index.mdx @@ -44,12 +44,11 @@ You can always manually trigger the Autofix flow from the Issue Details page. ### When Autofix Runs Automatically -When automation is enabled in your project's Seer settings, Sentry can also trigger Autofix automatically on new issues that meet the following criteria: +When automation is enabled in your project's Seer settings, Sentry can also trigger Autofix automatically on issues that meet the following criteria: -1. **Autofix automation is enabled** — The automation toggle in your project's Seer settings must be turned on. -2. **The issue has 10 or more events** — Sentry waits until the issue has captured at least 10 events to ensure it's worth investigating. -3. **The issue occurred within the last 14 days** — Only recent issues are eligible for automatic runs. -4. **The issue has a sufficient fixability score** — Sentry's ML model must estimate the issue is reasonably fixable (see below). +1. **The issue has 10 or more events** — Sentry waits until the issue has captured at least 10 events to ensure it's worth investigating. +2. **The issue occurred within the last 14 days** — Only recent issues are eligible for automatic runs. +3. **The issue has a sufficient fixability score** — Sentry's ML model must estimate the issue is reasonably fixable (see below). #### Fixability Score