Pausing protects your estimate
The expenditure algorithm only updates when it has enough evidence to update correctly. When your recent logging can't support a conclusion, the estimate holds at its last good value instead of drifting on bad data. Pausing is never a penalty — it's what keeps the number trustworthy.
The Expenditure screen shows a banner explaining exactly which condition isn't met, with a shortcut to fix it.
The reasons, and what fixes them
- Not enough history yet — right after you start (or restart), the algorithm needs a few logged days on record before it can begin updating. Just keep logging.
- Missing nutrition — it wants at least 4 days of food logged in the last 7. Below that, a week's average intake isn't meaningful.
- No recent weigh-in — it wants at least one weigh-in in the last 7 days. Without a fresh weight, intake can't be checked against anything.
- Stale weight — your last weigh-in is more than a week old. One step on the scale resumes updates.
Days that don't count
Two day-states interact with this deliberately:
- A day marked intentional fasting counts as a fully logged day of zero calories — fasting doesn't pause anything.
- A day marked incomplete logging is excluded from the calculation entirely — better to exclude a half-logged day than to let it read as a low-calorie day. Marking many days incomplete, though, can leave too few valid days and trigger a pause.
While paused, your targets stay where they are and your confidence level is preserved; updates resume automatically as soon as the missing data shows up.