Hide this message
Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at firstname.lastname@example.org
This article discusses over how and why an alert triggers again even after it has been acknowledged.
When creating or editing an alert, you have the option to control how the trigger actions for an alert reacts based on certain conditions. One of these is the ability to have an alert action trigger again after it has been acknowledged already, but has not yet reset.
The purpose of this is to make sure that if auto acknowledgements are in place or someone acknowledges the alert prematurely, the action will trigger again if the alert trigger condition is still true. In some ways, it can be considered as a "snooze" button.
NPM v11.5 and later
The execution settings section of "Do not execute this action if the alert has been acknowledged already (Recommended)" is not selected. When selected, the action is suppressed if the trigger condition is still present after the alert is acknowledged.