Why Time Tracking Apps Lose Data in the Background on iPhone

Quick answer

Yes — this is expected iOS behavior, not a bug in the app. iOS deliberately limits how long any app can run once it's off screen: a few seconds at the moment it's backgrounded, plus a short extension if the app explicitly asks for one. Beyond that, the system decides which apps get any background refresh time using its own heuristics, not a fixed schedule. For a time tracker holding a running session in memory, that's exactly the gap where minutes or hours can go missing. Below: what iOS actually does in the background, the three most common silent failure modes on iPhone, and how a well-built tracker — plus a couple of settings habits — closes the gap.

What actually happens when your tracker goes to the background

The few-seconds-then-suspend reality

The moment you leave an app, iOS gives it only a few seconds to act before it's expected to wrap up. It can ask for a short extension — up to a few more minutes — but once that window closes, iOS suspends the process outright. A suspended app can't run any code. It can't save a timestamp, can't sync to a server, can't do anything at all until you open it again.

There's no guaranteed refresh interval

It's tempting to assume Background App Refresh checks in every 15 minutes or so, like clockwork. It doesn't. Apple's own developer forums describe it as a range of heuristics deciding which apps get refresh time and when — and there are common, ordinary scenarios where an app gets no background time at all in a given session. That unpredictability is exactly why logging hours at the end of the day carries hidden risk: the longer a tracker leans on a live, in-memory counter instead of a saved timestamp, the more exposed it is to a background window that never opens.

Three silent failure modes on iPhone

Low Power Mode turns off Background App Refresh for everything

Low Power Mode explicitly disables Background App Refresh as one of its battery-saving measures, and iOS can switch it on automatically around 20% battery — no action aimed at your tracker required. If a session is running when that happens, the app quietly loses its ability to check in or sync until Low Power Mode is off again.

Force-quitting "to save battery" stops tracking on the spot

This is the most common one, because it feels like good phone hygiene. Swipe an app away in the app switcher and, per Apple's own guidance, it "might not be able to run or check for new content before you open it again". For a running timer that's not a delay, it's a hard stop, and nothing tells you it happened. Backgrounding an app by pressing the home button is safe; force-quitting it mid-session is not.

Aggressive background polling backfires

iOS also polices CPU use in the background and will kill an app that overruns its budget. A tracker trying to "stay alive" by polling hard in the background is more likely to get force-terminated, not less. The fix isn't fighting iOS for more background time — it's not needing it in the first place.

How well-built trackers avoid the problem

The pattern that actually holds up: save a start timestamp the instant a session begins, not a live counter that only exists in memory. On return to the foreground, recalculate elapsed time from that timestamp rather than trusting a background loop to have kept counting the whole time. Request a short background task window at the moment of backgrounding to get that save in immediately, then sync opportunistically the second the app comes back to the foreground so any gap closes fast. None of this needs continuous background execution — it just needs to not depend on it. That's the same design question behind what actually makes a time tracker good on your phone: reliability under iOS's real constraints, not more permissions.

A settings checklist for reliable tracking

A few habits close most of the gap on your end:

• Keep Background App Refresh on for your tracker specifically — Settings > General > Background App Refresh.
• Background the app with the home button or an app switch, not by swiping it away in the app switcher.
• Know that Low Power Mode changes this behavior automatically, and glance at your timer after a long low-battery stretch.

If you're already tuning iOS settings for deep work, setting up an iPhone Focus mode is a natural next stop — same part of Settings, same goal of getting your phone to work with your attention instead of against it.

How Pomlo fits in

This is exactly the problem Pomlo is built around. Every session starts from a saved timestamp, not a number counting up on screen, so a background suspension can't erase what's already been recorded — reopen the app and it's exactly where it should be. Focus sessions give you a clean start/stop for deep work specifically, and reports show you where the time actually went once the day's syncing is done, across iOS, Android, and the web, kept in sync automatically.

Pomlo is a beautifully simple time tracker for iOS, Android, and the web, built for freelancers, indie hackers, and small teams who want to track focused work, bill accurately, and ship more. Download it on the App Store or Google Play and stop wondering whether your timer kept up with you.

Frequently Asked Questions

Does force-quitting a time tracking app stop it from tracking?

Yes. Swiping an app away in the app switcher tells iOS you're done with it, and Apple's own guidance says a force-quit app "might not be able to run or check for new content before you open it again" — for a running timer, the session simply stops updating, and nothing alerts you that it happened.

Why does my iPhone time tracker lose time when Low Power Mode is on?

Low Power Mode disables Background App Refresh system-wide as one of its battery-saving measures. Since iOS can trigger Low Power Mode automatically around 20% battery, a tracker can lose its ability to sync or checkpoint a running session without you ever touching the tracking app.

Is background data loss an iPhone bug or expected behavior?

It's expected behavior, not a bug. iOS deliberately limits background execution to protect battery life and system resources — apps get only a few seconds at the background transition, plus a short extension if they explicitly request one, and the system's own heuristics decide whether an app gets any refresh time at all in a given session.

Conclusion

None of this is a flaw in your phone, and it's not a mystery bug in an app — it's how iOS has always managed background execution, on purpose, to protect battery life. The fix is mostly about how a tracker is built: timestamp-based sessions instead of a live counter, plus two habits on your end. Don't force-quit mid-session, and keep an eye on Low Power Mode. Get those right, and an iPhone quirk turns into a non-issue.