Why are duplicate alerts being generated?

Issue Title

• Duplicate alerts

Issue Summary

Duplicate alerts may be generated when the same event is processed multiple times, the device sends repeated event data, multiple identical or overlapping alert rules are configured, or the system does not correctly identify an event that has already triggered an alert.

Symptoms / How to Identify

• The same alert is generated multiple times for the same event.
• Multiple alerts have the same or very similar timestamp.
• Alerts contain the same vehicle, location, parameter, and event details.
• Multiple identical notifications are received for one event.
• The same alert appears repeatedly within a short period.
• Duplicate alerts may occur for one vehicle or across multiple vehicles.

Information Required Before Troubleshooting

Collect the following information:

• Vehicle/Object name or ID
• Device IMEI/Serial Number
• Alert name/type
• Date and time of duplicate alerts
• Alert IDs/details, if available
• Alert configuration
• Relevant Status/Raw Data
• Screenshots of duplicate alerts
• Number of times the alert was generated
• Whether the issue affects one vehicle or multiple vehicles
• Whether duplicate notifications are also being received

Troubleshooting Steps

Check on Device

• Check whether the device generated the same event multiple times.
• Review the relevant event parameter in the device data.
• Check timestamps of consecutive event packets.
• Verify whether the device is retransmitting stored data after a network interruption.
• Check whether the device is sending repeated or duplicate packets.
• Verify device configuration, firmware, and event-generation settings.

Check in System

• Review the duplicate alerts and compare their timestamp, vehicle, location, and event value.
• Open Status/Raw Data and check whether the corresponding event data was received multiple times.
• Verify whether multiple identical alert rules are configured for the same vehicle.
• Check whether multiple overlapping alert conditions could trigger the same event.
• Verify cooldown, repeat, duration, or duplicate-prevention settings, if available.
• Check whether the duplicate appears in the Alerts section, notification history, or both.
• Check whether the issue occurs with other vehicles using the same alert configuration.

Compare and Identify

• Device sends the event multiple times: Investigate device configuration, firmware, or retransmission behavior.
• Device sends the event once but system generates multiple alerts: Investigate alert processing or duplicate handling.
• Multiple alert rules match the same event: Review and consolidate the alert configuration.
• One alert is generated but multiple notifications are received: Investigate the notification channel rather than alert generation.

Possible Causes

• Device sending duplicate event data.
• Device retransmitting stored data.
• Network interruption and data resend.
• Duplicate alert rules configured.
• Overlapping alert conditions.
• Incorrect alert repeat/cooldown configuration.
• Incorrect event or parameter mapping.
• System processing the same event multiple times.
• Alert-processing or duplicate-prevention issue.

Resolution / Action

First determine whether the duplicate originates from the device, alert configuration, or system processing.

If the device sends duplicate event data, investigate device configuration, firmware, and network recovery behavior. If multiple alert rules are triggering the same event, review and modify the alert configuration.

If the device sends the event only once and a single alert rule is configured, but the system generates multiple alerts, escalate to the technical/system team with the vehicle ID, IMEI, alert details, timestamps, configuration, and relevant raw data.