Why health data can be missing

Missing is a state, not a measurement

A blank reading tells you that the app does not have a usable observation for that view. It does not tell you that the measured value was zero. No sleep record is different from a recorded night with no sleep, and no HRV reading is different from a low HRV measurement.

This distinction becomes important when apps calculate averages or trends. Inventing a zero can turn a connection problem into an apparent physiological change. Stride keeps missing information visible instead of manufacturing a measurement to make the dashboard look complete.

Follow the path the record travels

A Fitbit record must first reach its companion account through the device's sync process. Stride then reads supported information through Google Health with your permission. Those are separate steps. A nearby watch does not mean Stride is directly receiving every sensor observation over Bluetooth.

Apple Health follows a different path: compatible devices and apps write supported records into Apple's health store, and an authorized Stride build reads them there. A watch may display information that its companion app does not export to Apple Health. The existence of a number on a device does not guarantee its availability to another app.

Check the original source first

If a night or activity is missing, look for that specific date and data type in the original source. For Fitbit, complete the companion app sync. For Apple Health, check whether the relevant record is present. This separates an upstream recording problem from a later connection or import issue.

In a hypothetical example, yesterday's workout appears on your watch but has not reached the companion app. Repeatedly refreshing Stride cannot retrieve a record that is not available upstream. Once the source has the record, refresh the selected source in Stride and check any remaining warning.

Permissions are specific to the data

Health access is not always an all-or-nothing switch. Apple allows separate permissions for individual data types. You can permit steps while keeping another type private. Apple also intentionally prevents an app from knowing whether denied read access or absent records explains an empty result for a type.

Stride therefore cannot reliably diagnose every blank Apple Health view as a permission denial. Review access in the Health app when needed, then refresh Stride. A screen that says no records are available can be accurate even when it cannot tell you exactly why they are unavailable.

A successful sync can still be partial

Different data types may become available at different times or have different recording requirements. Sleep duration can exist without stages. A heart-rate summary does not guarantee daytime HRV. Some devices do not provide particular measurements, and third-party apps may share only part of the information they display.

Check the date and status of the specific view you are reading. Do not assume that one successful refresh makes every measurement current. If Stride reports a partial update, some existing observations may remain older than others. That is relevant context for interpreting both current values and derived estimates.

History has boundaries too

Stride's current Apple Health integration reads up to 60 days of available records. Availability also depends on what exists and what the app can read. This window is not a promise of 60 complete nights, and it does not imply that earlier records were removed from Apple Health.

Recovery calculations have another boundary: personal baselines require at least seven prior observations as well as suitable current inputs. If there are too few usable records, an unavailable recovery estimate may be the intended result. Waiting a week is not enough if the required observations were never recorded or imported.

Source selection prevents duplicate totals

The same workout or night can appear in more than one health system. Adding both sources could count it twice. In Stride, the selected source drives the health views and scores. Connecting both Apple Health and Google Health does not cause Stride to sum their totals.

When switching sources, check which one is active and expect its available history to determine the view. HRV methods and their baselines also stay separate: Stride currently reads Apple Health SDNN, while Fitbit uses RMSSD. A newly selected source is not guaranteed to recreate the same history or recovery estimate.

Know what disconnecting actually changes

Disconnecting Apple Health clears its imported view in Stride; system read permissions are managed separately in the Health app. Imported Apple readings are held in memory for the app session and are read again from HealthKit when needed. Your separate Stride account, Journal and plans have their own account storage.

Disconnecting Google Health stops new imports while existing Stride history remains. Account deletion is a separate action. Neither a missing dashboard value nor disconnecting a source means your original wearable records were erased. If a problem continues, contact Stride support with the date, source and affected view, without sending passwords, sign-in codes or health exports.

Sources and further reading

Sources explain the underlying concepts or product behavior. Research on other devices or apps is not validation of Stride.

See it in Stride.

Explore how Stride puts sleep, recovery, activity and habits into context, with the inputs and limits in view.

Check compatibility See availability