Skip to content
English
  • There are no suggestions because the search field is empty.

Why is the alert being generated with a delay?

Issue Title

  • Alert delay

Issue Summary

An alert may be generated with a delay when the event data reaches the system later than expected, the device transmits data after a network interruption, or the system takes time to process the received data and trigger the alert.

Symptoms / How to Identify

  • The vehicle event occurs, but the alert is generated later.
  • The alert timestamp is noticeably later than the actual event time.
  • The device data shows the event occurred earlier than the alert generation time.
  • Multiple alerts may be generated together after a period of connectivity loss.
  • The delay may occur for one vehicle, a specific device type, or multiple vehicles.
  • Notifications may also be delayed after the alert is generated.

Information Required Before Troubleshooting

  • Vehicle/Object name or ID
  • Device IMEI/Serial Number
  • Alert name/type
  • Actual event date and time
  • Alert generation date and time
  • Device data timestamp
  • System received timestamp
  • Alert configuration
  • Relevant Status/Raw Data
  • Screenshot of the alert
  • Whether the delay affects one vehicle or multiple vehicles
  • Whether the delay occurs with alert generation, notification delivery, or both

Troubleshooting Steps

Check on Device

  • Verify when the actual event occurred.
  • Check the timestamp generated by the device for the event.
  • Verify when the device transmitted the event data.
  • Check the device's GSM/network connectivity during the event.
  • Check whether the device experienced a network interruption.
  • Verify whether the device stored the event and transmitted it later.
  • Check the device's transmission interval and configuration.
  • Verify that the device clock/time settings are correct, if applicable.

Check in System

  • Open Status/Raw Data and identify the event data.
  • Compare the device timestamp with the system received timestamp.
  • Compare the system received time with the alert generation time.
  • Verify the alert configuration and trigger conditions.
  • Check whether any alert schedule, duration, or threshold could introduce a delay.
  • Check whether other alerts are experiencing similar delays.
  • Verify whether the alert was generated immediately after the required data was received.
  • If the alert was generated on time but the notification arrived late, investigate the notification channel separately.

Compare and Identify

  • Device generated the event late: Investigate device configuration, network, or device processing.
  • Device generated and transmitted the event on time, but the system received it late: Investigate network/communication issues.
  • System received the event on time, but generated the alert late: Investigate alert processing or system-side issues.
  • Alert was generated on time, but notification was delayed: Investigate WhatsApp, email, SMS, or notification service delivery.

Possible Causes

  • Poor or unstable network connectivity.
  • Device network outage and subsequent data retransmission.
  • Device storing event data and sending it later.
  • Incorrect device transmission interval.
  • Incorrect device timestamp.
  • Device configuration or firmware issue.
  • Network latency.
  • Alert processing delay.
  • System/server-side processing issue.
  • Notification service delay.

Resolution / Action

Compare the event time, device transmission time, system received time, and alert generation time to identify where the delay occurs.

If the device sends the event late, investigate the device, network, or configuration. If the system receives the event on time but generates the alert late, escalate to the technical/system team with the vehicle ID, IMEI, alert name, timestamps, configuration, and relevant raw data.

If the alert itself is generated on time but the notification is received late, troubleshoot the relevant WhatsApp, email, or SMS notification channel.