Fix delayed, missing or duplicated data

Record the newest source reading and its timestamp, the newest Nightscout reading, and the affected record type. Then follow the matching branch.

Glucose is delayed everywhere

Check the source app/cloud first. Cloud connections have different usual delays: Dexcom/Libre/Twiist glucose often 5–10 minutes, CareLink 5–20 minutes, and Glooko can be up to an hour. These are typical ranges, not guaranteed deadlines. See the route table.

Source is current, Nightscout is stale

Inspect the uploader status or Pro Connect Logs. If the error identifies expired/rejected authentication, follow that source’s reauthentication steps once. If the same error returns, report it instead of repeating setup. Check phone background restrictions when a phone uploader only works in the foreground.

Nightscout is current, follower is stale

Check the follower’s URL, readable token, refresh status and background permissions. Do not reset the CGM or add another uploader to repair a follower-only failure.

Glucose works, treatments or profiles are missing

Check whether the source route supplies the missing type. Dexcom Share/LibreLinkUp are not full pump treatment streams; Tandem treatments may arrive later than glucose. Provide one known source event and its time. Do not activate an override or enter a fake treatment to force an upload.

Duplicates or wrong times

List every uploader targeting the site and compare device/source names and timestamps. Keep one intended stream; use only documented combined connectors. Check the named timezone and device clock. Do not delete history in bulk before identifying the source of duplication.

Missing history after a transfer

Use the transfer completion and stalled-job guide. Today’s live readings do not prove that historical dates/collections copied successfully.

Support should retain the original evidence and completed attempts. Send only new details when continuing the same case.