Skip to content

Commit 2961040

Browse files
authored
chore(escalating): Clear up confusing intro sentence (#12415)
1 parent c64ddb1 commit 2961040

File tree

1 file changed

+1
-1
lines changed
  • docs/product/issues/states-triage/escalating-issues

1 file changed

+1
-1
lines changed

docs/product/issues/states-triage/escalating-issues/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: "Learn how the escalating issues algorithm works."
66

77
<Include name="merge-escalating-note.mdx" />
88

9-
By default, issues are archived until escalating. Sentry defines an issue as `Escalating` when the number of events is significantly higher than the previous week.
9+
By default, archived issues will transition to unresolved when the event count escalates. Sentry defines an issue as `Escalating` when the number of events is significantly higher than the previous week.
1010

1111
The escalating issues algorithm uses historical data from the previous week to calculate thresholds for the next week on a per-issue basis. If an archived issue exceeds its predetermined threshold, it gets tagged as `Escalating`, unless it was "[Archived Forever](/product/issues/states-triage/#archive)". An escalating issue is automatically surfaced in the "Unresolved" and "Escalating" tabs.
1212

0 commit comments

Comments
 (0)