The CtdappRunwayTooShort error should not be triggered after the CT is funded #716
Description
The CtdappRunwayTooShort error should not be triggered after the CT is funded. There should be an exception that will treat it as a healtly event.
Right now the runway is calculated as what's in the safe divided by the consumption per day. The comsumption per day seams to be negative when we receive funds (expected, as consumption is positive when we distribute funds).
Thus: total in safe / consumption is negative too, triggering the alerts as we are belong 0.
Possible solutions (some better than others):
-
do not trigger an alert of the consumption is negative
-
if you get a negative consumption, check if the wxHOPR balance is over 25k wxHOPR before triggering the alert.
-
if you get a negative consumption, check if wxHOPR balance went drastically up from the last alert