Ability to clear and not send notifications on Notification service startup.

Which version are you using?

In response to Stephen Kwan, "Which version are you using?" 2017 R2 (2.9.5.8424)

In response to Todd Jimeson, "2017 R2 (2.9.5.8424)" What you're describing should've been corrected in AF 2017 R2 (the version you're using). This screenshot is from the AF 2017 R2 release note:   Are you using PI Analysis Service 2017 R2 also?

In response to Stephen Kwan, "What you're describing should've been co..." We are on PI Analysis Service 2018 (2.10.0.8628) with automatic backfilling disabled. After rebooting the Analysis server, Duplicate Event Frames are created and some notifications are triggered again.

In response to Stephen Kwan, "What you're describing should've been co..." Yes, we're using PI Analysis Service 2017 R2. The problem is actually with restarting the Analysis service. It re-creates any open Event frame and orphans off the original. Notifications sees the new Event with no Notifications and dutifully sends another Notification. Both automatic recalculation and backfilling have been disabled.   This is the original alert: This shows the new event frame created after restarting the Analysis service: This shows the new event frame being closed but not the original event frame after the alarm condition has cleared:

In response to Todd Jimeson, "Yes, we're using PI Analysis Service 201..." Hi all, Would you please contact tech support with this issue?  It's not behaving as I'm expecting. -- Steve Kwan

In response to Stephen Kwan, "Hi all, Would you please contact tech su..." Adi or Todd, were you able to resolve anything with tech support?

FYI I have found a way to do this and I'll share it so that others know. 1.) Rename the Queue folder located under programdata\osisoft\pinotifications\data\servername 2.) Open System Explorer, click contacts, tools, delivery channels, right click on email, settings. 3.) Change the SMTP server to something fake. 4.) Restart the notifications service. 5.) Wait a few minuets 6.) Update the SMTP Server to the correct server name 7.) Restart the notification service. This will stop old or queued emails from being sent.

If this is implemented, the option to not send past notifications upon startup should be specified per notification rule and not globally, similar to the settings for retrying tasks in the Task Scheduler. Some notifications are not important after they are missed, but some are. One size does not fit all.

When the Notifications service is restarted, any alerts with an event that has not closed will be re-sent.  This is annoying and misleading.