One rule floods the Alert Centre or your inbox:
All fixes on this page are in the Firing policy section of the rule form. To change a rule you need Alert Rules with Edit. To stop only your own notifications, mute the rule for yourself instead. See Silence alerts at night or mute a rule.
While it stays true decides what happens after the incident opens. On every message notifies again on every message that still meets the condition. Remind every n notifies again at that interval. A repeat does not open a new incident; Fires counts them.
Check
Fix
With Confirm before alerting off, the incident opens on the first message that meets the condition. A value that hovers around the limit then opens and clears incidents over and over. Clears after works the same way for clearing.
Fix
If the condition comes true again while the incident is clearing, the incident stays open.
Cooldown between incidents silences a new incident for the same device or unit soon after the last one closed. Max per hour · per day caps the fires the rule sends for one device or unit. Fires over a cap still count, but send nothing. The hour runs in UTC; the day rolls over at local midnight.
Fix
Held-back incidents show the status suppressed and count under Suppressed today.
With Scope · evaluated set to Device, the rule opens one incident per device. A unit with two devices can open two incidents for the same event. One incident per, where the template offers it, splits further, for example one per geofence.
Fix
A limit that your units cross in normal work fires all day.
Check
Fix
Contact support@getgps.eu with: