Accidently “update(d) past entries” with an updated recipe. How do I undo that?

Here's the dialog to choose what you'd like to do when you save changes to a recipe.

If you make a mistake at this stage, you can edit the recipe again and update your past entries to put them back they way they were.

I hope that helps!

I ran across this because I just accidentally did the same thing and this is really something that I feel should be a setting in the app somewhere. You should be able to specify that you never want to update past entries-- it shouldn't be as easy as it is to accidentally wipe out dozens or hundreds of entries with specific data.

I use this feature primarily for food that I make in large batches-- smoothies, soups, etc... --and I have found that this is a great method of getting almost exact data rather than using a random store bought food that is hopefully close. Because I don't want dozens upon dozens of custom recipes, I will take the basic recipe and update it with the specifics that I'm changing for this batch, use that recipe for half a dozen meals, then update it again when I make a new batch.

If I make a green smoothie, for instance, it probably has spinach, some type of fruit, lemon juice, some type of nut, maybe yogurt, and water in it. But the ratios are almost never exact because the fruit size and type changes based on what I have on hand-- a banana one time, cantaloupe another, pineapple after that-- and I tend to just eyeball the other ingredients and measure as I go. Now that I have overwritten those entries, I am probably never going to be able to see the exact macro- and micro- nutrients that I was trying to log for when I visit a nutritionist or my primary care doctor. I can't "update them back to to the way they were" because they consistently change. At best, I can try and average out the recipe (guessing at that, because I don't have details) to try and make it be somewhat accurate.

I probably can't complain too much, because I'm not really using this in the form that it was originally intended, but I honestly don't see a good reason to ever update past entries unless you find out that you had an error in a recipe you almost never change. And if you're using the custom recipe option like that (admittedly, probably the expected use case), then double and quadruple checking that you really want to erase data (or forcing someone to go modify a setting) wouldn't be much of an inconvenience while the current process seems to irrevocably erase data and permanently corrupt your data with a simple slip of your finger that accidentally touches the wrong button.

I exported up to August of this year, so I'm losing 3 months of data, rather than 7, but this is still really painful and it has a good chance of happening again because I don't see a good option for handling my use case other than custom recipes and I really don't want to create hundreds of these in the app.