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.
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.
Would be nice to be able to specify a horizon of "how current must a notification be" for issuance
Vijay Singh commented
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.