Almost every “Helix is broken” report turns out to be a data problem, not an app problem: the watch wasn’t worn, a permission is off, or Apple Health never recorded the signal in the first place. Each section below walks the checks in the order that finds the cause fastest.
No recovery score this morning
One rule explains most cases: no night of data means no score. Helix will not invent a number from a missing night.
- 1
Was the watch on your wrist overnight?
The most common cause by far is a watch that spent the night on its charger. If it charged overnight, there is no overnight data to score, and this morning is simply a gap. - 2
Is the sleep in Apple Health?
Open the Health app and check whether last night’s sleep was recorded. If Health has no sleep session, Helix has nothing to read. - 3
Are permissions granted?
In the Health app, check that Helix has read access to sleep, heart rate and HRV. A single revoked permission can silently remove an input. The install & permissions page lists what each one feeds.
HRV or vitals missing
Check the raw data first: if Apple Health doesn’t have it, Helix can’t read it.
- 1
Look in the Health app
Find the metric (HRV, respiratory rate, wrist temperature) in Health and check whether last night has samples at all. This one check tells you whether the problem is upstream of Helix. - 2
Check the fit
A watch worn too loose records poorly overnight. Snug it one notch before bed; overnight vitals need consistent skin contact. - 3
Consider the night and the hardware
Very short sleep gives the watch little time to sample some metrics. And older Apple Watch models lack some sensors entirely, wrist temperature for example, so those rows will always be empty. Helix shows missing signals as missing and scores from the ones it has.
My day didn’t roll over, or strain reset at a weird time
Helix does not start your day at midnight. The day rolls over when you wake from your main sleep, which is what keeps a late-night workout attached to the day you actually did it. The sleep-anchored day page explains the model in full.
- 1
Check when your main sleep ended
Your Helix day began when that sleep ended. If you slept unusually late, the rollover was late too, by design. - 2
Rule out a nap being read as main sleep
A long daytime nap is treated as a nap, not a new day; only your main sleep rolls the day. If a very long, oddly timed sleep got classified as main sleep, the rollover follows it. Check what Health recorded for the session.
Complication or widget looks stale
- 1
Open the app
Widgets and complications display the latest snapshot the app published; they don’t compute anything themselves. Opening Helix recomputes and republishes it, which fixes most stale numbers on the spot. - 2
Check watch connectivity
For complications, make sure the watch is connected to the iPhone (or on Wi-Fi) so the fresh snapshot can reach it. See complications & widgets for how freshness works.
A workout didn’t count toward strain
Strain requires real heart-rate presence. A workout logged without heart-rate data would need Helix to fabricate cardiovascular load, and it won’t.
- 1
Open the workout in Apple Health
Check whether the session has heart-rate samples attached. A manually logged workout, or one from an app that records no HR, carries none. - 2
Scores feel wrong after travel or illness
Baselines are personal and recent history matters. Jet lag, a fever, or a week off shifts your overnight physiology, and your rolling baselines take a few days to follow it.
- 1
Give it a few days
After a disruption, expect scores to read conservative while the baselines re-center on the new normal. That lag is a feature: a body under travel or illness stress usually is less recoverable than it feels. - 2
Keep the data flowing
The fastest recalibration is simply consistent nights of data. The baselines page covers how the window works.