Database Update after App Update causes Data Gap / No Record in AT4

Hi @dagguet, thanks for the detailed screenshots. They make this easy to walk through.

The good news first: the backup activity you spotted isn’t the cause here, and it can’t be. Backups (including the catch-up that works through your long history) only ever run in sleep mode, when the app isn’t actively recording your movement. The moment recording starts, any backup in progress yields to it immediately. Recording always takes priority, so a backup can’t pause, slow, or stop it. The backup you saw and the recording gap happened around the same time, but one didn’t cause the other.

That also means the app already does what you asked for, which is reassuring. It only backs up when you’re stationary and idle, never while you’re out and moving, and never at the expense of recording. So “only back up in stationary mode, and don’t let it stop recording” is already how it works today.

The part actually worth looking at is the recording gap on its own. That looks like a separate issue we’re digging into right now: occasionally recording goes quiet while the app is still running, and picks back up when the app is next opened. There’s a thread following it here: No Movement in AT4 but full day in AT3 — your screenshots fit the same shape, so that’s the best place to follow progress.

(The gap not showing in the timeline, just extending the neighbouring stay, is the separate known one I mentioned last time, BIG-444. Still on the list.)