Loop reporting 0 IOB following bolus

[shrkath]

Describe the bug
A clear and concise description of what the bug is. I.e. what you see vs what you expect to see.

Attach an Issue Report
Tap the Loop settings icon on the bottom of the screen, then tap Issue Report and attach it to this ticket.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Phone

• Hardware: iPhone 13 pro
• OS Version: iOS 26.0

Loop Version

• Version Number: 3.8.2 via Browser Build

CGM

• Device: Dexcom G7

Pump

• Omnipod DASH

Additional context
Add any other context about the problem here.

Loop Report 2025-12-18 00:06:19-05:00.md

[marionbarker]

Can you clarify your issue.

• Did you update the "pump time" because of a seasonal time change?
• Was there a significant change in the current value for ISF or CR because of the pump time change?
• Loop will recalculate the recommended dose following the update of pump time
• One thing to look out for: Does your ratio of ISF/CR change abruptly during the day? This can cause issues with the model used by Loop to develop bolus recommendations.

Please read this section of LoopDocs.

• https://loopkit.github.io/loopdocs/faqs/time-faqs/#time-zones-daylight-savings-time-summer-time

[shrkath]

Hi Marion, There was no time change, we didn’t travel. The time change was earlier this year, we are in Pittsburgh, PA - we didn’t make any serious adjustments to the settings - my ISF is stable during the day -CR goes down during the day, but what had happened was within 30 minutes. Within 30 minutes my son received more than 17U of insulin. Thanks a lot, Katherine

…

On Tue, Dec 23, 2025 at 13:48 Marion Barker ***@***.***> wrote: *marionbarker* left a comment (LoopKit/Loop#2385) <#2385 (comment)> Can you clarify your issue. - Did you update the "pump time" because of a seasonal time change? - Was there a significant change in the current value for ISF or CR because of the pump time change? - Loop will recalculate the recommended dose following the update of pump time - One thing to look out for: Does your ratio of ISF/CR change abruptly during the day? This can cause issues with the model used by Loop to develop bolus recommendations. Please read this section of LoopDocs. - https://loopkit.github.io/loopdocs/faqs/time-faqs/#time-zones-daylight-savings-time-summer-time — Reply to this email directly, view it on GitHub <#2385 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWTJWSAG46WUQA542KKRO334DGE6LAVCNFSM6AAAAACPMNO6POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBXGYYTGNZXGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[marionbarker]

I did not connect this Issue with the person who sent me an email. I was keying off the name of the Issue, which says: "Time change leading to boluses". Thank you for posting the Loop Report.

I will try to summarize what I think happened. Included later is an excerpt from your email.

In future - providing exact time stamps and both a Loop Report and a Critical Event Log is important.

Is this still happening?

Have you had a recurrence of a time when Loop shows 0 IOB following a bolus?

Phone is iPhone 13 Pro running iOS 26.0

• I would suggest you update that phone to 26.2 at your earliest convenience.

Overview

If I am understanding correctly:

• The problem you are reporting is that boluses were issued but Loop did not record them as IOB
  • Then because the bolus was not recorded as IOB, Loop continued to provide automatic dosing
  • The screenshots you sent via email were from Dec 16, before you deleted the app and showed
    • a 7 U manual bolus followed by a series auto-boluses of 2.8 U
    • a second 7 U manual bolus (because the app continued to show 0 IOB) with more auto-boluses of 2.8 U
    • in the screenshots, Loop reported IOB of 0 U
• You completely deleted the app and reinstalled a fresh version
• You said the same thing happened again with the fresh install morning of Dec 17 (see email excerpt below), although you opened the Loop and did not bolus again)
• The report you provided above was with the fresh install
• Unfortunately, while a LoopReport contains up to 84 hours of pump/CGM data, it truncates other information - which is why we ask for a Critical Event Log - which has a full 7 days of information
  • If you issue a critical event log now it will no longer have data from Dec 17, but if you did issue one earlier and saved it, please post it

Review of Loop Report

Your timezone is UTC - 5, so a UTC timestamp of 2025-12-17 01:52:48 for cannula insertion corresponds to a pod change at local time of 20:52 (about 9 pm) on 12/16. That is the beginning of the log file you posted, which is consistent with the app being deleted and installed fresh just before that pod was inserted.

I examined the Loop Report. Although there are many Manual Boluses recorded, there are no Automatic Boluses. There are Automatic Temp Basal reported - so perhaps you switched to Temp Basal Only for the dosing method.

The pod messages are consistent with open loop starting just before 7 am on Dec 17 and continuing until 11 pm that same day.

The table below is an excerpt of some of the information parsed from the Loop Report you posted.

UTC Time	Local Time	What	Comment
2025-12-17 11:41:19	6:41	Manual Bolus, 6.55 U	Breakfast
2025-12-17 11:54:40	6:54	Open Loop	I'm assuming this is switch to open loop. Following bolus, Loop switch to auto temp basal of 2.5 U/h, until TB was cancelled and scheduled basal started
2025-12-17 14:35:01	9:35	Manual Bolus, 3 U	Snack?, still scheduled basal only
2025-12-17 17:18:46	12:18	Manual Bolus, 4 U	Lunch, still scheduled basal only
2025-12-17 20:55:17	15:44	Manual Bolus, 1 U	??, still scheduled basal only
-	-	-	continued manual bolus and scheduled basal only
2025-12-18 04:09:31	12/17 23:09	Temp Basal 0 U/hr	closed loop resumed
2025-12-18 04:59:29	12/17 23:59	Temp Basal 0 U/hr	end of report

Excerpt from the email

Excerpt from the email with added dates inserted in parentheses in a few places. And "d/c" means "delete/discontinue" - you completely deleted the app from the phone and installed fresh. (This process also deletes any data that might be available for diagnosing what happened. So in future, please issue a Loop Report and a Critical Event Log before deleting the app.)

• this past Sunday evening (12/14) I rebuilt . . . and got Loop 3.8.2 (4), it all seemed to be fine
• on Monday 12/15 evening the pod expired and after I changed the pod the glucose readings didn’t match the dexcom, the curve and the number on top. I was advised to d/c ape health glucose readings, which I did and everything went back to normal.
• that night 12/15-12/16 my son was very low and though I was giving him glucose and was expecting hom to go up appropriately, his iob was always 0 or -0.5, he didnt.
• on Tuesday am we dialed him 35g for breakfast and heard the pump started clicking. Then like after breakfast my Mom’s loopcaregiver again suggested 7U. We looked at his screen and saw that his iob was 0. He also had multiple 2.5 boluses from loop. We opened his Loop and still send him to school, he then had multiple juices and tabs and 2 snacks and his lunch with no entrances of either carbs or insulin. So he was true low.
• in the late evening (12/16) I d/c the Loop app and installed another one from test flight. It did seem to be working.
• then in am (12/17) we had again the same scenario. Loop clicked in the bolus for breakfast and shortly suggested the same amount to be dialed in. We opened Loop again before it had happened.
• i dont see the insulin entrances in nightscout since that time.

I apologize for all the disorganized details. I got very scared. I am not tech savvy but was doing ok for 5 years with both sons just following instructions.

Photo from Dec 16 of son's phone.