At the facility where I work, we need to have near-real-time notification of certain events. I recently created an event frame to be triggered when a digital PI point switches from a value of "Normal" to a value of "Alarm". I received word today that such an event had occurred, but no notification went out. When I looked at the event frames, there was nothing showing for the most-recent event. I checked the archive history for the point that should trigger the event, and sure enough it had shown a value of "Alarm" for about five minutes. Without having changed any aspect of the analysis, I performed a Backfill/Recalculate on the analysis to see what might happen, and doing that caused it to capture the event and (belatedly by fifteen minutes) send out the notification.
What should I look for to understand why the event frame failed to generate organically? Are there any known issues that might contribute to this behavior?
EDIT: I did discover that the notification trigger on the template, under Options related to child event frames, had the option selected "When the severity is higher than any previously true trigger condition" instead of "When any trigger condition is true". However, this analysis should not trigger child event frames, so I'm not sure that option changes anything.
Thanks,
James Aylard
