Charge and rest start from previous day value i.o. empty state

[bartmuskala]

NOOP version

10.1.1

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

Data was still offloading and charge and sleep had value of the day before.

What you expected instead

No data until data is offloaded and properly processed.

Steps to reproduce

Wait for tomorrow 😁

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).

[ryanbr]

Thanks — the two screenshots are enough to see it's real. Charge 68 and Rest 89 are identical across both days while Effort correctly differs, so this isn't the intended "carried from last night" display (that one is dimmed and captioned). Today's row genuinely holds yesterday's scores.

Likely cause: the night read-window opens 30h before the day starts, so mid-offload it can still see the previous night and score it as today's.

To confirm, could you attach your export? More → Export → NOOP backup (.zip) — it'll show which sleep session the 19 Aug row was scored from. A strap log from the same sync helps too (Settings → STRAP LOG → Save…).

No rush, and your expectation is the right one — it should show no data until the night has actually landed.

[ryanbr]

Correction on the path — it's More → Backup & Sync, not "Export". Strap log is still Settings → STRAP LOG → Save…

[bartmuskala]

Let me start with the strap log. The backup is quite large.

noop-strap-log-260820-0815.txt

[bartmuskala]

Today the night data seem to have synced over night before looking this morning. There was another score, not the previous day's although going to sleep after midnight. The score for both charge and rest changed after the final part synced. This is only temporary but it should not happen like that. One expects one score, not a two step scoring. Thanks for looking into this.

[ryanbr]

The log shows it clearly — thank you, that's exactly what was needed.

Your night was scored four times while data was still arriving:

time	in-bed samples	RHR floor	HRV	sleep
00:21 (asleep)	5,564	52	45.5	92 min
08:03	15,646	44	—	—
08:05	—	—	64.1	246 min
08:13	32,185	42	—	—

The big offload landed at 08:04:59 (103,798 rows) and everything moved with it — HRV up 41%, resting HR floor down 10 bpm. So the first score was computed from a fraction of the night, while you were still asleep.

You're right that it shouldn't work that way. The fix is to not publish a score for a night that's still in progress, and show the "carried from last night" state until the night has actually landed — which is what you expected.

Note this is separate from what your original screenshots showed (19 Aug repeating 18 Aug's values). I'll track that one separately rather than assume they're the same cause; your backup would still help there when convenient.

One thing worth mentioning: you're exempt from battery optimisation, which is why NOOP syncs overnight at all. That part is working as intended — the bug is only that scoring didn't wait.