Werk #5745: handle deferred notification properly
| Component | Notifications | ||||
| Title | handle deferred notification properly | ||||
| Date | Mar 2, 2018 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
After the first retry deferred notification did not respect the cooldown time defined in the global settings anymore. Furthermore the counting of the configured retries was not done properly. If e.g. a retry count of one was specified actually three retries were performed. These two issues have now been fixed.