[Bug][Combo] Many successful boli trigger alarm "bolus failed"

[yossibivas11]

I use 3.3.2.1 and Combo. Most meal boli trigger "bolus failed" in AAPS but are in fact successful both in the pump and also written correctly in the AAPS graph.
Thanks!

[MilosKozak]

you must provide more info if you need help

[Der-Schubi]

I can confirm this. @dv1
I think this has something to to with the RunningMode changes made to dev in April.
After using the Bolus Calculator (but also when using normal bolus) when the bolus dialog is open and bolus is in progress, you can see the status bar (bottom of main screen) in the background say "Connecting for xx s". Then after the bolus, the bolus dialog is hidden and the main screen still shows "Connecting for ..." and the bolus failed alarm is triggered and the entered carbs are deleted . At the same time, the Combo screen shows "Last connected: Less than a minute ago", but "Last bolus: x U (xx m ago)" is still the older bolus. The pump is still connected at this time and the driver pulls the recent bolus from the pump history. But the carbs are already deleted.
See screenshots, the second one is taken a few seconds after the first.

This is shot after the bolus is finished and bolus dialog is hidden:


AndroidAPS.log