How are background sync gaps and payload size handled?

Background sync gaps are usually end-user-side: the wearable hasn't synced to its app, battery-saving mode is on, or (for mobile SDKs) background refresh is…

Background sync gaps are usually end-user-side: the wearable hasn't synced to its app, battery-saving mode is on, or (for mobile SDKs) background refresh is disabled or background delivery isn't implemented. The per-provider debugging FAQ covers each case.

For payload size:

• Responses are automatically chunked only when the requested range exceeds about 28 days.

• For smaller ranges that are still too large, request shorter windows (e.g. 5-day intervals), or ask for payloads to be delivered as a download URL instead of inline data.