# Icinga Flapping Detection prevents "resolved" notifications from being sent

**URL:** <https://community.icinga.com/t/icinga-flapping-detection-prevents-resolved-notifications-from-being-sent/9726>\
**Category:** Icinga Web\
**Tags:** notifications, icingaweb2\
**Created:** [April 27, 2022, 5:32pm UTC](https://community.icinga.com/t/icinga-flapping-detection-prevents-resolved-notifications-from-being-sent/9726 "2022-04-27T17:32:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anand.vikash](https://community.icinga.com/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@anand.vikash](https://community.icinga.com/u/anand.vikash)\
**Post date:** [April 27, 2022, 5:32pm UTC](https://community.icinga.com/t/icinga-flapping-detection-prevents-resolved-notifications-from-being-sent/9726/1 "2022-04-27T17:32:41Z")

</div>

Title: Icinga Flapping Detection prevents “resolved” notifications from being sent

Description: Let us understand the the scenario with below use case  
/ example. Please find the list of events below(where 1 - denotes the oldest event/state and 6 - is the latest event/state of a service in Icinga) that can be seen in the history of an Icinga service.

1. An alert triggers (Service becomes in critical state)
2. Notification sent to Pagerduty(Incident management system)
3. Flapping turns ON
4. Alert resolved (Service becomes in OK state)
5. Flapping turns OFF
6. Service remained in OK state (but no notification was sent for recovery from critical to OK)

Notification was never sent to Pagerduty(Incident management system) about the service being back up/recovered from critical to OK state (because service/alert check became OK during flapping, when notifications are suppressed) - incident remains unresolved in Pagerduty(Incident management system).

Please let us know the possible solution, so that the resolution notification must be sent.

Other information:

- Icinga Web 2 version - 2.9.5
- Used modules and their versions (System - About) -
- Web browser used - chrome(100.0.4896.127)
- Icinga 2 version used -
- PHP version used -
- Server operating system and version - GKE cloud

---

<div class="post-metadata">

**Author:** ![rivad](https://community.icinga.com/user_avatar/community.icinga.com/rivad/32/5852_2.png) [@rivad](https://community.icinga.com/u/rivad)\
**Post date:** [April 29, 2022, 3:01pm UTC](https://community.icinga.com/t/icinga-flapping-detection-prevents-resolved-notifications-from-being-sent/9726/2 "2022-04-29T15:01:21Z")

</div>

Maybe a config error or a bug.

What are the filters on the notification object attached to this service and the user object?  
Have you looked at [https://icinga.com/docs/icinga-2/latest/doc/15-troubleshooting/#notifications-troubleshooting](https://icinga.com/docs/icinga-2/latest/doc/15-troubleshooting/#notifications-troubleshooting)?

Possibly better to open a issue on Github?

---

<div class="post-metadata">

**Author:** ![moreamazingnick](https://community.icinga.com/user_avatar/community.icinga.com/moreamazingnick/32/7725_2.png) [@moreamazingnick](https://community.icinga.com/u/moreamazingnick)\
**Post date:** [May 2, 2022, 6:36am UTC](https://community.icinga.com/t/icinga-flapping-detection-prevents-resolved-notifications-from-being-sent/9726/3 "2022-05-02T06:36:18Z")

</div>

> [@anand.vikash](#):
>
> Icinga 2 version used -

there are recent fixes of some notification bugs, but you left your icinga version empty so who knows if updating will solve this problem
