I have a weekly study goal that I only need every few months, not on a regular basis. I’m not sure when I’ll use Beeminder for it again, but I probably will.
Is there a way to pause it indefinitely?
If you’re confident you’ll think of it again when it’s a good time to bring it out, archiving the goal would probably make sense! But otherwise you could also just set the slope to 0 for now! EDIT: Now that I think about it, maybe 0 slope is a premium feature. So archiving is probably what you want.
I used to archive goals regularly. Nowadays, I tend to only do it if I plan to never resume the goal, and I just set the slope to 0 if I am not planning to actively do the thing for a while.
The key benefit of setting slope to 0 for a period of time is that it eventually starts up again, rather than being forgotten about!
Indefinitely flat goals are broadly discouraged, but the Take a Break feature on the Stop/Pause tab can be used to flatten any goal for a specified period.
It isn’t, at least for now! (Not allowing it is something we’ve talked about, but use-cases like this might be arguments against that.) Setting the rate to 0 indefinitely or for a period would be a good answer – but archiving is probably equally fine too for most use-cases, and is probably the easiest way of avoiding mistakes and getting it restarted again with the right settings when wanted.
sorry, where do i put the slope to 0? i’ve adjusted the commitment dial to 0 and nothing happened.
Without looking at the goal in question, it’s hard to know what the problem might be. If you’ve made the change and hit the “commit” button, though, then the problem is most likely the akrasia horizon – any such changes never kick in immediately, but take effect after seven days. You’d see the line going flat, seven days ahead, in that case. If that seems like the problem, it’d be helpful to hear more about what wasn’t clear there, how we could make that more obvious, etc.
If you can’t see a change on your graph seven days away, and you’re sure you made the change to your commitment and hit submit, can you send support@beeminder.com an email explaining the problem and link us to the goal? Then we can troubleshoot further!
email sent.
For anyone wondering, the reason was that hi123 had graph changes planned ahead, and the change would only take place after those.
In addition, the goal’s cumulative end total required was set to 0, but not the rate, which would’ve also added to the confusion.