I had spoke with Nicky when I first ran into this thinking it was a bug, but after realizing this was normal behavior I thought it peculiar that scheduling a break for, say, a month from now, locked in the rate the activity is currently at.
I had created a test beeminder to demonstrate.
If I create a beeminder at rate 7 per week today today, and schedule a break from 10-1 thru 10-02 and then attempt to adjust the steepness of the road today to 10 per week, it doesn’t kick in until the break occurs two months from now.
I think the behavior I expected from this was if I were to schedule a break for October, changes to the road gauge would kick in before the scheduled break or rate change, and be maintained after the break (the latter of which does work).
Furthermore, there doesn’t seem to be a way to fix this if done by accident (as I did) I assume without using the (Visual or Regular) Road Editor. But, nominally, the road editor (non-visual at least) is under Beemium.
First, why is the break behavior like this? It feels inflexible to schedule breaks as a consequence as a new user, as it completely clamps down the flexibility of changing the road gauge for the following week for scheduling too far in advance. Are breaks not meant to be scheduled that far out, only directly on the Akrasia horizon?
Secondly, I believe that an option to cancel breaks or cancel future rate changes for non-beemium accounts would be useful, unless the Visual Road Editor is meant to be accessible to all users, as in the documentation there lacks a clear answer to what to do if you accidentally type in the wrong numbers for a break or scheduled rate change.