Skip to content

When pod runs dry during a bolus, Loop appears to record the intended amount rather than the delivered #2648

Open

Description

@bkhx

I had a Dash pod that showed 0 insulin remaining. To use up any remaining insulin in the pod I issued a manual bolus of 4u, running Loop v3.14.10 (57) (dev) workspace SHA 6de1c92. After about 2.5u were delivered the pod alarm sounded as expected, but the spinner and numeric counter on the main screen continued as if additional insulin continued to be delivered, stopping at an indicated 4u delivered. The behavior I would have expected is for the count to stop when insulin delivery stopped, showing either a time-based approximation of the actual amount delivered, or a calculated amount from the pod's actual delivery report.

After I filled and started to the next pod, I looked at the loop display and the graph continues to show a delivery of 4u rather than a revised number to reflect the amount actually delivered, and the event history also shows no correction to that value. The behavior I would have expected is for the insulin delivery graph to be updated to show the actual amount delivered rather than a triangle marking the amount commanded. And in the event history I would have expected to see either a revised number on that bolus record to show the amount actually delivered, or some subsequent line item showing a negative amount as a correction if the original line item in the event history should remain unchanged---at present the event history does not accurately reflect the actual amount of insulin delivered.

I don't know whether this is merely a display issue, or whether the Loop algorithm is now operating on an incorrectly high IOB value; unfortunately I did not make a record of the Active Insulin value before and after this bolus.

The bolus in question shows in the event history as Bolus 4U Nov 2 at 7:07PM. On the Loop main page screenshot it shows as the second of 3 boluses; the 3rd bolus was given after the pod change.

I attach the Loop main screen screenshot, the Loop event history screenshot, and a Loop issue report.

iPhone 17 Pro MG7M4LL/A; iOS 27.2; Loop v3.14.10 (57) (dev); Dexcom G7 10-day, Dexcom app SW12300;
Omnipod Dash lot PD1U04162621 firmware 11.7.0

Image Image

LoopReport2026-11-02-19-26-21-05-00.md

Activity

  1. ps2 commented on Nov 3, 2026

    @ps2
    Collaborator

    Thanks for the detailed report and the Loop report. They show the cause.

    When the pod faulted, it reported 1.8 U of the bolus not delivered, so about 2.2 U went in. Loop only applies that amount if it reads the fault while the bolus is still scheduled to be running. Here it read the fault a few seconds after the bolus would have finished, so it kept the full 4 U.

    To your question: yes, active insulin was overstated by about 1.8 U, not just the display. That error shrinks as the bolus ages and is gone after the insulin duration (6 hours).

    Fix: loopandlearn/OmnipodKit#211 (dev) and loopandlearn/OmnipodKit#212 (next-dev). The bolus will be recorded as ending at the fault time, with only the delivered amount.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions