Inactivity
Inactivity triggers when a tag hasn't reported a position for a specified duration.
How it works
The system tracks when each tag last reported a position. If the time since the last update exceeds the threshold, the rule triggers. This catches tags that have gone offline, lost power, or moved out of hotspot range.
The alert says where the tag was last seen, and which registered Agent device saw it there: "Cage 42 inactive for more than 24 hours, last seen in Customer Site X by Bob's TC52". When the tag was outside every zone, the alert gives its last position instead: "last seen at 52.19570, 0.16900". The place and the name reach every channel (dashboard, email, Slack, webhook), so the reader knows where to look and whose device to start with, without opening the asset.
Skip zones where a tag may go quiet
Some places are allowed to swallow a tag for a while: a customer site that keeps roll cages for days, or a store room with no coverage. Add those zones' keywords under Skip assets last seen in zones with keywords. A tag last seen in a zone that carries one of the keywords does not alert.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
max_inactive_duration_seconds |
integer | No | 3600 | Maximum time without a position update before triggering (default: 1 hour) |
exclude_zone_tags |
array | No | None | Zone keywords. A tag last seen in a zone with one of them does not alert. Up to 10. |
device_tags |
array | No | None | Only evaluate tags with these asset keywords |
exclude_device_tags |
array | No | None | Skip tags with these asset keywords |
Example: tag offline alert
Alert when any tag hasn't reported for 2 hours:
- Max inactive duration: 7,200 seconds (2 hours)
- Severity: High
- Apply to: All tags
Common causes of inactivity
- Tag battery depleted
- Tag moved out of hotspot coverage
- Hotspot offline or disconnected
- Tag powered off