A trip is missing or on the wrong vehicle
A recorded trip that isn't where you expect it is usually on another vehicle, not gone. Here's how to find it, move it, and what to check when one's truly missing.
Before assuming a trip vanished, it's worth knowing that "missing" almost always means "somewhere else" — most often recorded against a different vehicle. Those can be moved. Genuinely-never-recorded trips are a smaller list of causes, below.
Move a trip to the right vehicle or driver
Open the trip and tap Wrong vehicle or driver? Reassign this trip.
Pick the correct Vehicle (and driver, if you're an owner or admin), add a Reason, and confirm with Reassign trip.
Owners and admins can change both the vehicle and the driver. A driver can correct the vehicle on their own trip within 48 hours of it. The reason is kept on the trip, and any fine or FBT record that came from it moves across too.
If a driver is simply in a different car now, the fix going forward is to change who's driving — that re-points everything from this point on, so you're not reassigning trip by trip.
When a trip is genuinely missing
Work down this list:
- It hasn't synced yet. A trip appears once it's finished recording and reached our end. Give it a few minutes on a connection.
- It's on another vehicle. Check the vehicle you didn't expect — reassign it with the steps above.
- The driver had no vehicle allocated. Trips need a vehicle to record against; an unallocated driver's trips have nowhere to land.
- The trip was very short, or fell outside the tracking schedule window, so it wasn't recorded by design.
If trips have stopped altogether rather than one going astray, it's almost always permissions — see My trips aren't recording.
Last updated Wed Aug 12