Hi @Tony_M , thank you for adding this. I checked this further, and I think your explanation adds an important nuance. My earlier reply was too absolute when I said that an Inside Area notification may only be sent after the exception ends.
The more accurate explanation is that the exception has a start and an end, and notifications can be associated with both points. An initial notification may be generated when the exception is created, and a further or final notification may be generated when a long-running exception closes. Whether both are sent can depend on the rule, notification type, and how the event is processed.
There is also a separate possibility of an actual delivery delay. If the device data arrives late, the device is unable to communicate, or the notification-processing pipeline is delayed, the first notification may not arrive until later. In that situation, the email timestamp does not necessarily represent when the vehicle first met the rule condition.
The condition itself still affects when the exception starts:
- Entering Area is the most appropriate condition for a security alert when the goal is to know that a vehicle entered a restricted zone.
- Inside Area represents an ongoing state while the vehicle remains in the zone.
- Stopped inside zone must first establish that the vehicle has stopped.
For customers using these rules for security, I would recommend testing with an Entering Area rule and comparing the device timestamp, exception start time, exception end time, notification-created time, and email-delivery time. That should show whether the behavior is related to the rule condition or to data/notification delivery.
Thanks again for sharing your experience. It is a helpful distinction.
Eishi FUN