Ah, interesting, thanks for sharing your question! So, whatever slope the graph has calculated, it’s based on the two factors you set when changing goal date and goal total. If you set the end date and the end total, the third factor of rate has to be auto-calculated… it can’t physically be anything else! That’s because the goal total you set isn’t a cap, it’s a target. It’d be interesting to know whether there’s anything weird/inconsistent that made you think you were setting a cap rather than a desired target, if you can remember!
In this case I am pretty sure that I never set end date (goal was created long time ago, via API, so maybe I am not remembering it).
I had set rate, without actually set end date as it was an open ended goal (maybe due to technical detail some fake end date was set - there are some traces of that in statistics panel) and I added goal total, expecting that end date will recalculate.
Instead of that slope got recalculated.
I am not sure what would be difference between cap and target in that context (not a native speaker, it seems to have an equivalent meaning in this context).
It’ll depend on which two fields were white and which one was greyed out. If we re-calculated the rate when it was active/white, then that sounds like a bug! Can you give me a link to the goal?
A “cap” is an amount you don’t want to exceed, but it may not be the number you want to reach. A target is the number you actually want to reach, and Beeminder assumes you want to hit that number exactly (rather than just not exceed it).
Can you send that request to firstname.lastname@example.org? Best to keep that sort of thing all in one place, probably! (And then people don’t get in the habit of requesting it on the forum and trusting to my non-existant omniscience. )