Repository navigation
No effort at all on a day is hard to believe, HR always does something #983
Description
NOOP version
9.2.2
Platform
Android
OS version
16
WHOOP strap model
WHOOP 5.0
Where the data is coming from
Live Bluetooth (strap connected)
Test Centre profile
Not a test-mode bug
What happens
We did a city trip today. It was mostly walking, but to make sure we were somewhere in time, we walked rather fast.
The app shows 0 effort despite some HR changes during the day. Definitely not a zero state.
What you expected instead
I would expect some HR activity that would at least account for a low score. I guess whoop would easily score it 5, maybe 7.
Steps to reproduce
Nothing.
Strap log
Before you submit
- I attached my exported NOOP .zip (not a screenshot of the Live screen). If my bug is a clearly reproducible UI issue I described exactly how to see it instead.
- I attached or pasted a strap log above — or my bug is a clearly reproducible UI issue that doesn't need one (e.g. a typo, a button that does nothing) and I've described exactly how to see it.
- I checked the Troubleshooting guide — especially "history syncs but no data" (most often the strap isn't banking history to flash; charge it to 100% and reconnect).
- I checked the FAQ and — if I'm on a WHOOP 5.0 / MG — the 5.0/MG status page, and this isn't an already-known limit (e.g. SpO₂, or recovery/sleep on the 5/MG).
- I've left out anything personal (strap serial, account email, raw export).
Activity
ryanbr commentedon Jul 30, 2026
Not a data problem — the HR was read fine. This is the scoring model doing what it was built to do, and I think you have found a real limit of it.
Effort only starts counting once your heart rate is above roughly half your heart-rate reserve — the midpoint between resting and maximum. Below that line a reading contributes exactly nothing, no matter how long it lasts. Fast walking usually sits just under that line, so a whole day of it can genuinely add up to zero. That is why the card says a calm day reads near zero.
One thing worth checking on your side: make sure your age (or a max-HR override) is set in the profile. If it is not, the app assumes 30 years old, which puts your maximum — and therefore that counting line — as high as it goes, and makes a zero much more likely than it should be. Setting your real age lowers the line and may be enough on its own for a day like this to register.
On the wider point, I agree with you. A brisk 4-hour walk is not a rest day, and a metric that can only answer "zero" for it is not telling you the truth about your day. Worth saying plainly though: the alternative model already in the app swings the other way and would score that walk higher than the 5-7 you would expect from WHOOP, so this is not a one-line switch. Leaving this open as the place to work that out.
Thanks — this is the third good one from you today.
Workouts: save the session's own denominator, not a re-read one (#983)
Workouts: thread the same resting HR into the saved workout's calories (
Workouts: score the SAVED workout with the measured resting HR (#983) (…
bartmuskala commentedon Jul 31, 2026
I have my age set to 45 and my max HR to 188 (because it is that high 😉). That explains why it read close to 0. However this morning the score for yesterday was all of a sudden 2.8. Seems post processing adjusted the metric?
I can live with a low 2.8 instead of more. But not with a 0. The brisk walking example of 4 hours does not feel like 'no effort'.
This is the adjusted page for yesterday.
Release 9.3.0 (#1000)
Workouts: score the SAVED workout with the measured resting HR (ryanb…
Release 9.3.0 (ryanbr#1000)
Workout mode for the Live Activity ("Zone Glass")
Pin live/saved kcal parity; record the Zone Glass plan