At times I have event frames that generate late for various reasons that trigger a notification. Since it was late we have no need to get the notification. I would like a way to not have a notification trigger if it is late.
ADMIN RESPONSE
Aug 20, 2022
How would we determine if it's too late to send a notification? This needs to be evaluated by the PI Notifications Service and not be a human being.
Please provide your input.
Jonathan Gibbs
May 20, 2025
Every month our company does windows patching and when the analysis service reboots it sends out email notifications that are months in the past. I have to email a very large group of users in the company to disregard the bogus pi system notifications that were sent out due to patching. I wish I did not have to do this. Could the system be designed to tell that a notification already went out and to not send another one upon service restart?
We are sending messages for Huge machine start stop in case messages are missed/delayed can give wrong information to users i.e. we sent stopped messages when machine was actually resumed from stopped to started. Delayed messages creates havoc to users and they rush to machinery and founds that machine is running.
The notification template settings could allow for an optional late notification period. If the analytic execution time s more than a specified time behind wall clock time, then the business may not need the event frame notification.
Every month our company does windows patching and when the analysis service reboots it sends out email notifications that are months in the past. I have to email a very large group of users in the company to disregard the bogus pi system notifications that were sent out due to patching. I wish I did not have to do this. Could the system be designed to tell that a notification already went out and to not send another one upon service restart?