Skip to content

Failed bolus uncertain  #944

Closed
Closed

Description

@claraloop

Describe the bug
Bolus error uncertain
No clicks heard bg did not drop after 30-40 min
Event was logged as 1,4 units uncertain
It stayed there . Husband erased it he was trying to make loop forget it so that it would bolus our son insulin again.
It still shows in apple health. It was given today at 16:55 1,4 units

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 5 se
  • OS Version: iOS 12.1

Loop Version

  • Version Number: [e.g. 1.9.2]
  • Repo: omnipod

CGM

  • Device: Dexcom G6
  • Manager app: Dexcom App

Pump

  • Manufacturer: omnipod
  • Model: [e.g. 723]
  • Firmware version: [e.g. 2.3A 1.1 0B 0B]

Additional context
Add any other context about the problem here.

Activity

  1. claraloop commented on May 2, 2019

    @claraloop
    Author

    I can’t find the attachment icon?

    1f0527572c030e010001b1

    • 2019-05-02 16:41:06 +0000 receive 1f052757300a1d080189b800002973ff8041
    • 2019-05-02 16:50:12 +0000 send 1f05275734030e01008197
    • 2019-05-02 16:50:15 +0000 receive 1f052757380a1d080189b800002997ff82c9
    • 2019-05-02 17:00:15 +0
  2. claraloop commented on May 2, 2019

    @claraloop
    Author

    Can’t attaché at the moment will try later from computer

  3. tkk41 commented on May 14, 2019

    @tkk41

    here the same, initiated a bolus, but didn't start.
    RL was close to the pod approx 50 cm

    I have run "Test Command" (see screenshot)
    Attached is the issue report (created after running the Test Command)

    Test Command

    Loop Report 2019-05-13 09_23_15+02_00.pdf

  4. github-actions commented on Nov 7, 2023

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  5. github-actions commented on Nov 21, 2023

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions