Skip to content

Use the cgm event upload key and continue with cgm events in uploadCgmEventData - #2636

Merged
ps2 merged 1 commit into
next-devfrom
fix/cgm-event-upload-key
Nov 1, 2026
Merged

ps2 merged 1 commit into
next-devfrom
fix/cgm-event-upload-key

Conversation

@ps2

@ps2 ps2 commented Nov 1, 2026

Copy link
Copy Markdown
Collaborator

uploadCgmEventData was copied from uploadPumpEventData and kept two pump-event references:

  • its UploadTaskKey used .pumpEvent, so CGM event upload failures were counted and retried against the pump event task
  • when the query anchor advanced it continued with uploadPumpEventData(to:), so when more CGM events remained than one batch, the next batch waited for the next upload trigger while pump events were re-uploaded

Both now use the CGM event path, and the error log says "cgm event". The dispatch queue and query anchor already used .cgmEvent.

Verified that Loop builds; RemoteDataServicesManager has no unit tests.

…mEventData

The cgm event upload counted failures against the pump event task and,
when more cgm events remained than one batch, ran the pump event upload
again instead of fetching the next cgm event batch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant