Skip to content
English
Customer portal
www.uffizio.com
  • There are no suggestions because the search field is empty.

Why was the alert not generated?

 Issue Title

  • Alert not generated

Issue Summary

An alert may not be generated when the configured alert condition is not met, the alert is inactive or incorrectly configured, the device does not send the required data, or the system fails to process the received data and trigger the alert.

Symptoms / How to Identify

  • The expected alert is not visible in the Alerts/Notifications section.
  • The vehicle/device performed an action that should have triggered an alert, but no alert was generated.
  • No alert record is available for the expected date and time.
  • The required device data is available, but the corresponding alert is missing.
  • Other alerts for the same vehicle may be working normally.

Information Required Before Troubleshooting

Collect the following information:

  • Vehicle/Object name or ID
  • Device IMEI/Serial Number
  • Alert name/type
  • Date and time when the alert was expected
  • Actual event that should have triggered the alert
  • Alert configuration/settings
  • Alert activation status
  • Relevant Status/Raw Data
  • Screenshot of the alert configuration, if available
  • Whether the issue affects one vehicle or multiple vehicles
  • Whether other alerts are being generated successfully

Troubleshooting Steps

A. Check on Device

  • Verify that the device was Online when the event occurred.
  • Check whether the device generated the data required for the alert.
  • Open the device's latest available data and verify the relevant parameter.
  • Check whether the required event value, such as speed, ignition, location, temperature, or other sensor data, was received.
  • Verify that the device is transmitting data at the expected interval.
  • Check for any device, GPS, network, or sensor-related issues affecting the required data.

B. Check in System

  • Verify that the alert is enabled/active.
  • Check the alert configuration and triggering conditions.
  • Verify that the correct vehicle/object, group, or user is assigned to the alert.
  • Check the configured thresholds, geofence, time period, or other conditions.
  • Check Status/Raw Data to confirm that the required event data reached the system.
  • Check the Alerts/Notifications section for the expected date and time.
  • Verify whether similar alerts are being generated for other vehicles.
  • Check whether any alert restrictions, schedules, cooldowns, or duplicate-prevention settings apply.

C. Compare and Identify

  • Required event data was not generated by the device: Investigate the device, sensor, GPS, or network.
  • Required data reached the system but the alert was not generated: Check alert configuration and system-side processing.
  • Alert was generated but notification was not received: Troubleshoot the notification channel separately.
  • Alert works for other vehicles but not this vehicle: Check vehicle assignment and device-specific configuration.

Possible Causes

  • Alert is disabled or inactive.
  • Incorrect alert configuration.
  • Incorrect threshold or trigger condition.
  • Vehicle/object is not assigned to the alert.
  • Required device data was not received.
  • Device was offline.
  • GPS, network, or sensor issue.
  • Alert schedule or time restriction prevented the alert.
  • Alert cooldown or duplicate-prevention setting prevented generation.
  • System-side alert processing issue.

Resolution / Action

Verify that the alert is active and correctly configured for the required vehicle/object. Confirm that the device generated and transmitted the data required to satisfy the alert condition.

If the required data is available in the system but the alert is still not generated, escalate the issue to the technical/system team with the alert configuration, vehicle ID, IMEI, event timestamp, relevant raw data, and screenshots.