Currently, as I understand it, Beeminder has a patch to fix some problems, and this patch makes it so that the derail condition is something like:
IF you were in the red at your last deadline,
and IF you will be in the red at the next deadline if no additional data points are entered,
This is, of course, a counterintuitive derail condition that will often cause derails when it shouldn’t.
Because of this problematic derail condition, numerous other patches were introduced to fix these problems, and these in turn cause other problems, and so forth.
So it seems likely that there is a whole cascade of bugs resulting from this one incorrect derail condition.
And there are probably others as well.
From the new user’s perspective these issues are very confusing and not explained clearly, and result in frustrating things like random unexplained derailments and inability to retrorachet with cryptic error messages.
I understand this is being worked on, so thank you! I’m putting this here because I think it’s likely that there are many issues resulting from this “mother of bugs.”
While there may be technical issues with this, from my perspective the most natural derail condition would be to check only at the time of deadline, and then patch up whatever issues result from this.