Originally Posted by
mr_belowski
Interesting. So when you made the voice command was the answer (15 seconds) about right?
The app is choosing to derive the gap at the last minute, just before the message is read (rather than when it's queued). It can do this if the message queue is long, to prevent the queued message being stale by the time it's read. It sounds like the app is actually getting the last laptime rather than the gap when it does this. I'll dig into the code there, it's possible that I've just miss-tagged the message payload and it's telling the delayed resolution code to insert the wrong information