-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug] Backfill from G7 Created Bad Data #2291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The other side effect of this is I'm not able to find or delete the erroneous entries in Apple Health, but they're still present in Loop. If this is a one-off with just weird sensor data it's probably not a bug. The other three entries given were correct values. I'd be happy to help out with a fix if doing something like "if backfill data is in the future, we should ignore it" is an option. |
Sorry not to respond earlier. Were you able to resolve this? If so how. |
The only way I could resolve (other than waiting 10 days) was to wipe the phone and reinstall loop. |
Describe the bug
G7 data that was backfilled appears to have incorrect timestamps, which is leading to bad future data.
Attach an Issue Report
Loop Report 2025-03-04 22:57:27-04:00.md
To Reproduce
N/A - Seemed to randomly happen
Expected behavior
When data backfills, it should have timestamps that are not in the future.
Phone
Loop Version
CGM
Pump
Additional context
No matter what I try I cannot get this data purged. I'm thinking because it's missing the uuid it cannot be deleted, but I'm not sure.
If you look in the attachment, this seems odd:
The first three backfills are timestamped ~10 days ahead. This could very well be an issue with Dexcom, but wondering if it's come up before. Thank you!
The text was updated successfully, but these errors were encountered: