How your data flows
Two common routes are:
- Sensor or pump → phone/APS uploader → Nightscout → follower.
- Sensor or pump → manufacturer cloud → Pro Connect → Nightscout → follower.
A cloud route can be delayed even when the phone has a current reading. A follower adds another download step. Check the timestamp at each point instead of assuming the whole chain works because one screen is current.
Different records follow different rules
Glucose readings, insulin/carbohydrate treatments, pump status and treatment-setting profiles are separate data types. Dexcom Share and LibreLinkUp glucose connections do not supply a full pump treatment/profile stream. A source may have a slower treatment upload than glucose.
The compatibility guide gives each route’s limits. A historical transfer is a separate job from continuing live uploads.
Find where an update stops
- Note a new reading in the source app/cloud, including its time.
- Open Nightscout and find that reading.
- If Nightscout has it, check the follower’s last-update time and authentication.
- If Nightscout lacks it, inspect the configured uploader or Pro Connect Logs.
Use one intended uploader per data stream. Documented combined connectors manage their source roles internally; do not add parallel glucose uploads to repair a missing treatment stream.