Why was the wrong alert generated?

Issue Title

• Wrong alert generated

Issue Summary

A wrong alert may be generated when the system receives incorrect or unexpected device data, the alert conditions or thresholds are incorrectly configured, the wrong alert is assigned to the vehicle, or the system incorrectly processes the received data.

Symptoms / How to Identify

• An alert is generated even though the configured condition did not occur.
• The alert type does not match the actual vehicle/device event.
• Alert details such as vehicle, time, location, speed, or parameter value are incorrect.
• An alert is triggered at an unexpected threshold.
• The alert is generated for the wrong vehicle/object.
• The raw device data does not support the alert that was generated.

Information Required Before Troubleshooting

Collect the following information:

• Vehicle/Object name or ID
• Device IMEI/Serial Number
• Alert name/type generated
• Expected alert condition
• Actual event that occurred
• Date and time of the alert
• Alert configuration and threshold
• Alert details/screenshot
• Relevant Status/Raw Data
• Whether the issue occurs once or repeatedly
• Whether other vehicles are generating the same alert incorrectly

Troubleshooting Steps

A. Check on Device

• Verify that the device was transmitting data when the alert was generated.
• Check the relevant parameter received from the device, such as speed, ignition, GPS, temperature, sensor status, or other event data.
• Compare the device-generated value with the actual vehicle/device condition.
• Check whether the device is sending unexpected, incorrect, or fluctuating values.
• Verify the device configuration and relevant sensor/input settings.
• Check device GPS, network, sensor, and hardware status where applicable.

B. Check in System

• Verify the alert configuration and trigger condition.
• Check the configured threshold, duration, range, geofence, schedule, or other conditions.
• Verify that the correct vehicle/object is assigned to the alert.
• Check the alert's parameter mapping.
• Open Status/Raw Data and compare the received value with the alert condition.
• Check the generated alert details, including timestamp, location, value, and vehicle.
• Check whether multiple alerts with similar conditions are configured for the same vehicle.
• Verify whether any alert hierarchy, priority, schedule, or rule configuration could have triggered the alert.

C. Compare and Identify

• Device sends incorrect data: Investigate the device, sensor, wiring, GPS, or configuration.
• Device sends correct data but alert condition is incorrectly evaluated: Investigate alert configuration or system processing.
• Correct alert condition is configured but the wrong alert type is generated: Check alert mapping/rule configuration.
• Alert is generated for the wrong vehicle: Verify vehicle/object assignment and alert configuration.

Possible Causes

• Incorrect alert configuration.
• Incorrect threshold or trigger condition.
• Wrong vehicle/object assigned to the alert.
• Incorrect parameter mapping.
• Device sending incorrect data.
• Sensor or device configuration issue.
• GPS inaccuracies.
• Multiple overlapping alert rules.
• Incorrect alert duration or schedule.
• System-side alert processing or rule evaluation issue.

Resolution / Action

Compare the generated alert with the device data and configured alert condition. Correct the alert threshold, rule, parameter mapping, vehicle assignment, or device configuration as required.

If the device is sending correct data and the alert configuration is correct but the system still generates the wrong alert, escalate to the technical/system team with the alert details, configuration, vehicle ID, IMEI, timestamp, and relevant raw data.