A list of GPS trackers that are not reporting brings together devices without recent information, but their situations can be very different. It may include an interruption that has just become prolonged, a vehicle temporarily withdrawn from work and a tracker whose follow-up has remained open for days. Plaspy's Devices not reporting block separates them by the age of their last report. That age becomes useful when you connect it with what you still need to know about each device.
After reviewing a fleet for several weeks, some names may become familiar on this list. It is easy to overlook them or to treat every entry as a new hardware fault. A more useful review recovers the context behind each absence: which device it is, when information stopped arriving and whether the operation still expects to track it. That conversation can also reveal differences between the recorded inventory and the vehicles actually at work.
Time without data needs an operational explanation
Consider three illustrative cases. One device has not reported for six hours and belongs to a vehicle undergoing work confirmed by the workshop. A second last reported nine days ago; the company says that vehicle has temporarily stopped providing services. A third has been silent for more than a day while remaining assigned to its usual route. These are hypothetical situations, rather than diagnoses of actual devices.
Ordering the cases by age helps you find them and recognize how long each information gap has remained open. Duration alone cannot explain what happened. The oldest entry may have a known context, while another needs an explanation for information the operation expected to receive. Understanding the list means connecting the timeline of the data with the timeline of the work.
For the workshop vehicle, knowing that work is underway provides context but does not prove that the intervention caused the interruption. You can ask what happened to the tracker during that work. For the vehicle taken out of service, the relevant question may be whether tracking is still needed during storage. For the third, you need someone familiar with the current situation of both the vehicle and its device.
The same age column therefore leads to different questions. The block helps bring those questions together without relying on memory to identify devices that stopped updating. A useful review establishes what information is missing in each case and which agreement or check could recover it. It does not require assigning one explanation to every name on the screen.
Three windows for examining older reports
In Plaspy, Not reporting means the last report is more than five hours old. The block lets you choose More than 5 h, More than 24 h or More than 7 days. Each choice changes the set being examined. The first gives a broader view of prolonged gaps; the others focus on devices whose missing information has already extended beyond a day or a week.
These distinctions are useful when reconciling devices that have remained unresolved for some time. Looking beyond seven days may reveal names that need a conversation about their place in the inventory. Returning to more than five hours brings back the more recent cases excluded from that view. A filter organizes the scope of a review; the other devices still need consideration under the appropriate arrangements.
The block's bar distributes cases into age bands, and each list entry shows how long it has been since the last report. Those elapsed times continue to advance without new information arriving. A gap moving from hours into days describes the continuation of the same absence. It does not establish that a second fault occurred or that the vehicle's physical condition changed.
The wording “more than” also matters. A device exactly at the five-hour boundary has not exceeded it. When comparing an earlier view with the current list, a few minutes may explain why a name has entered the category. There is no need to attribute that classification change to an intervention or another incident without further evidence.
The dashboard blocks documentation explains these periods and the related states. They are criteria used by the Plaspy view, rather than a rule establishing how long any vehicle may go without supervision. Your operation's need for information may require a check before a device appears in this particular list.
A device without positions raises a different question
The block separately counts devices that have no position. Keep that distinction when reviewing them. For a tracker that previously provided information, an earlier reference exists from which to start a conversation. For one without positions, that reference has yet to be established in the available information. Describing both as devices that stopped working yesterday would conceal this important difference.
Suppose a company has recently added vehicles and expects to find them on the map. A name entered in the platform does not, by itself, establish that installation has been completed or that a position has arrived. Reviewing that case requires someone familiar with registration and commissioning. The starting question is which part of that process has actually been confirmed.
A device with a position from last week provides a different starting point: what changed afterwards? There may be information about workshop work, a device transfer, a service change or a situation that has not yet been communicated. These possibilities guide questions. The age of the report cannot choose one of them as the proven explanation.
Separating these groups also improves the account you give of the fleet. Devices awaiting their first position and devices that stopped reporting represent different information needs. Different people may be able to answer, and different facts may allow the review to progress. Combining them into one explanation makes it harder to recognize what remains unknown in each case.
Familiar names can conceal changes to the inventory
A recurring entry deserves more than remembering that someone has already discussed it. Is the tracker still installed in the same vehicle? Is the same person responsible for knowing its situation? Does the company still expect tracking information during this period? These questions concern the relationship between the record and the operation. The growing time without reports helps bring them to attention but cannot answer them.
In the example of a vehicle temporarily withdrawn from service, someone may confirm that it remains in storage. That settles part of the context. The company still needs to establish whether it expects to monitor the vehicle there. Taking it out of revenue-generating or operational work does not automatically remove the need to track it. The purpose of that tracking should be agreed by whoever holds the relevant responsibility.
If a device has been transferred, correctly identifying both the tracker and its current vehicle matters before communicating an older location. A familiar name may preserve an association that has changed in practice. Compare it with installation records and the authorized person's information, rather than inferring the relationship from the area containing the last point on the map.
Correcting a name does not turn the last report into an observation of the new vehicle. If the tracker was transferred after sending that report, the position belongs to its previous installation. Establishing the new relationship requires confirmation of the transfer and later information, alongside the relevant record updates. Otherwise, a point transmitted under an earlier association could be communicated as the current vehicle’s location even though that conclusion has not been established.
This is not a reason to remove records simply to shorten the list. A long gap does not establish that a device should be retired. There may be an ongoing monitoring need, pending work or historical information the company wants to retain. An administrative change should follow a confirmed situation and the decisions of the person responsible for the account.
The inventory review becomes useful when it reveals something that no longer matches the operation. The vehicle may still be working while nobody has resumed its case, or a temporary withdrawal may have an expected return date. Recovering that context allows a specific next commitment to be agreed, instead of accepting a permanent place for the same name on the list.
A technical conversation starts with an identifiable reference
When technical help is needed, saying only that the GPS is not working gives little shared context. Identifying the device, its last report time and what changed around that moment creates a clearer starting point. If you compare that time with workshop work or a phone call, use a common time reference. The dashboard presents times in the account's time zone.
It also helps to distinguish direct knowledge from assumptions. Workshop attendance may be confirmed without anyone knowing whether the tracker was disconnected. A data service may be subscribed to without communication at that location having been checked. The person examining the device needs that distinction to decide what further information to request, instead of starting with a cause treated as established.
Depending on the case, the missing reports may require checks of power, installation, connectivity or service. The block does not identify which of those explains the gap. If a service expiry also needs attention, retain it as a separate issue: changing a commercial date is not, by itself, evidence that communication has resumed. Administration and confirmation of received data need to remain distinguishable.
A well-prepared technical question also states the limits of the available information. The last position remains a historical reference until a new location is confirmed. Sharing it with its time can explain what is known, but it should not be presented as a current point or evidence of everything that happened during the gap. This keeps the operational and support conversations consistent.
What changes when you return to the list
A shorter list on the next visit can have several explanations. A device may have supplied newer data, you may have changed the age filter, or the selected group may be different. Before counting recovered cases, identify what happened to the devices that no longer appear. A difference between totals does not automatically equal a number of restored connections.
The total can also remain unchanged while the situation evolves. Imagine one device examined yesterday resumes communication and another joins the list today. The count is the same, but there is a recovery to verify and a different gap to understand. Remembering only the total hides both developments. Identifying the devices reveals this change in the cases without confusing a stable number with a stable operation.
For a temporarily withdrawn vehicle, its expected return date may be the next useful reference. At that point, the tracking agreement needs to be compared with the information available again. An explanation that was sufficient during storage may no longer be enough when the vehicle returns to work. Time changes the need to know its situation even if its name remains on the same list.
A new report with a recent timestamp establishes that later information has arrived. If the case required tracking to resume, that is relevant evidence for continuing the assessment. It does not independently explain the gap or complete the missing interval. Follow-up through your team's usual arrangements can distinguish what has been recovered from the questions still requiring an answer.
To preserve the scope of a review, record the group and age filter alongside the cases actually examined. This work record is separate from the block and can be as simple as your operation needs. It lets the next review build on identifiable facts instead of depending on a remembered number that has already changed. A block can also use a different group from the dashboard's main selection; a scope change needs to be recognized before entries or departures are attributed to improved service.
The Dashboard requires an account or subuser with access to more than ten devices visible on the Map. Permissions limit what each person can consult. The Dashboard guide explains these conditions, while the guide to organizing blocks and groups covers the view's scope. Example dashboards in the demo let you explore the interface without representing your actual inventory.
When you next encounter a GPS tracker that is not reporting, recover its context: the last information, the device it belongs to and what the operation still needs to know. The elapsed time then becomes more than a number increasing on screen. It provides a reference for a relationship, check or commitment that has remained unresolved.