Fuel & alertsFleet alerts
Alert detail — layout and map
Summary, vehicle, type-specific blocks, notes, attachments, action log, and map with history.
Open and return
From the alerts inbox, open an alert. Back returns to the list.
If the detail request fails, you see Failed to load alert. or Alert not found. Use Back and open the alert again, or confirm it still exists.
Left column
Typical sections (depending on alert type and API payload):
- Header — alert type name (some deviation types show Alert Details instead of a prefixed title).
- Summary — message and triggered time.
- Vehicle — vehicle card (movement status may display as a static label in the UI).
- Type-specific blocks (when present), for example:
- Geofence Details — geofence name, criteria name.
- Inactive Telemetry Detail — last telemetry time (relative).
- Harsh Brake Detail — speed at event (km/h).
- Internal Notes — note text and author display when a note exists; otherwise placeholders explain that notes will appear after they are added.
- Attachments — list with download/open behavior when files exist.
- Action Log Timeline — chronological audit entries (assignment, false alarm, violation, etc.).
Right column — map
A map shows the alert in context with history track when the API supplies geometry. Interaction follows the standard map component for your deployment.