You see one of these:
- The rides explorer of a schedule reads "No rides yet".
- A ride shows Late or Incomplete although the unit kept to the timetable.
- A checkpoint shows Missed although the unit drove past it.
- Automatically create rides is off
- The unit is not assigned to the schedule
- The schedule is expired or not yet active
- The ride never started at the first checkpoint
- Checkpoint radius or order is too strict
- The tolerance or expiration time is too short
- Unit checkpoints are not in route reports
With Automatically create rides off, the live detector records no rides for the schedule. It is off by default.
Check
- Open the schedule.
- In step Route & basics, look at Automatically create rides.
Fix
- Turn on Automatically create rides.
- Save the schedule.
The live detector records rides for the schedule's units from then on.
See Schedule wizard.
A schedule records rides only for its own units.
Check
- Open the schedule at step Units.
- Look for the unit's card.
Fix
- Add the unit with Add Units / Groups.
- Save the schedule.
See Change the units on a schedule.
A Fixed date schedule runs once, inside its Active From and Active To window. The schedule list shows Scheduled before Active From, and Expired after the end.
Check
- In the schedule list, look for the Scheduled or Expired badge.
Fix
- For a timetable that repeats, use Daily time or From activation instead of Fixed date.
- For a one-off run, set Active From and Active To to the right window.
See Route schedules and rides.
A ride opens when a unit enters the first checkpoint, or leaves it if the unit was already there. A unit that joins the route halfway never opens a ride.
Check
- Open the unit's track for the day on the map, and see whether it passed the first checkpoint.
Fix
- Make sure units start at the first checkpoint of the route, or reorder the checkpoints. See Edit or clone a route.
Each checkpoint has a radius in metres, default 100. For a location or unit checkpoint, the unit must come inside that circle; a geofence checkpoint uses the geofence outline. A depot gate 150 metres from the point never counts.
Checkpoint Order decides which visits count:
- Strict: a checkpoint counts only after the one before it.
- Skipping Possible: the unit may skip checkpoints but cannot go back. This is the default.
- Arbitrary: any order.
Check
- Select the ride card in the rides explorer.
The track and the checkpoints draw on the map.
- Look whether the track enters each circle, and in which order.
Fix
- Raise the radius of checkpoints that the track misses by a little. See Route form.
- If the units visit stops in a different order, change Checkpoint Order to Skipping Possible or Arbitrary.
A unit that arrives up to the tolerance after the arrival time is on time; later is Late. Expiration time ends a ride that stays open too long, which makes it Incomplete and leaves the rest Missed.
Check
- In the ride's detail card, read Live Status for each checkpoint. A late checkpoint shows how late.
- Compare that with the tolerance in step Checkpoint timing.
Fix
- Raise the tolerance. Set common variation time (min) sets it on every checkpoint at once.
- Raise Expiration time if rides end before the last checkpoint.
- Save the schedule.
The explorer shows "Recalculating rides for the updated schedule…", then the corrected rides.
The route reports skip unit checkpoints, because a unit has no fixed place. A checkpoint that follows another unit shows in the rides explorer, but not in Ride log, Route adherence or Checkpoint performance.
Fix
- Use a location or geofence checkpoint for any stop you report on.
See About routes and checkpoints.
Contact support@getgps.eu with:
- The route name, the schedule name and the unit name.
- The day of the ride, with your time zone.
- The status you see and the one you expected.