We have made adjustments to unify the stop arrival, completion and failure timestamps, as well as the events history. We have also adjusted our apps to compensate client-side clock skew.

We are tracking arrived_at, completed_at, and failed_at timestamps on stops, as well as keeping a separate events history. So far, there could be discrepancies between the individual timestamps of these events between the events history and the dedicated timestamps - we have adjusted our stop completion logic to keep those aligned so the timestamps will always match.

We have also made adjustments to the completion of grouped stops, where we now ensure the corresponding grouped stops will also have the same timestamps throughout, matching those on the initial completed grouped stop.

Additionally our driver apps now handle clock skew in a better way - if the clock on the device of a driver is incorrect, so far the resulting stop timestamps could be wrong from the actual time the corresponding arrival or completion events occured, both in offline as well as online stop completion. We will now adjust those timestamps according to the real time based on the delta of the driver’s device clock to the actual time.