Describe the Bug
If a grouped alert triggers during a bucket evaluation but the condition subsides in a later bucket within the same execution cycle, the alert fails to auto-resolve. It stays in the ALERT state indefinitely because the history object fails to reset to OK when a bucket drops below the threshold.
Steps to Reproduce
- Create a grouped alert with multiple consecutive windows.
- Trigger the alert so a group breaches the threshold.
- Allow the metric to drop below the threshold.
- The alert never fires a "Resolved" notification and remains stuck in the UI.
Expected Behavior
When a group's metric drops below the alert threshold, the history state should reset to OK, which in turn triggers the auto-resolve webhook/notification.
Describe the Bug
If a grouped alert triggers during a bucket evaluation but the condition subsides in a later bucket within the same execution cycle, the alert fails to auto-resolve. It stays in the
ALERTstate indefinitely because the history object fails to reset toOKwhen a bucket drops below the threshold.Steps to Reproduce
Expected Behavior
When a group's metric drops below the alert threshold, the history state should reset to
OK, which in turn triggers the auto-resolve webhook/notification.