What is your goal?recover multiple steps in a scenario that were not save.
What is the problem & what have you tried?created scenario with many steps, tested, worked, (Didnt save) closed. upon returning discarded changes.
tried history but the last steps are not there, checked the last run, but the steps arent there either.
Hello,
You can submit your ideas here:
https://www.make.com/en/platform-ideas
There is already autp-save feature idea so you can upvote it:
https://www.make.com/en/platform-ideas/p/scenario-builder-autosave
There is also very interesting draft-version idea:
https://www.make.com/en/platform-ideas/p/scenario-builder-save-scenario-as-draft
I completely understand your point.
At the same time, there is also a downside to this- sometimes you may want to test something in your scenario or validate a rough idea by utilizing existing scenario, and in such cases auto-save could be just as problematic as not having it.
So without scenario versioning, I prefer to save my scenarios manually 
i personally rather loose what im testing than loosing real work… anyway, seems this is been an issue since 2022…
As I said- without version control, auto-save is as problematic as the lack of this function.
Let’s say you are testing mapping or accidentally remove a colon from JSON.
With autosave, you will spend hours debugging the scenario once you forget to turn it off.
In my opinion - this will cause as many problems as we potentially could have now while not saving the scenario. So I’m not suprised that this is waiting for that long to be implemented.
You are about a week too early. The auto-save feature and recovery is currently being tested and will be implemented very soon.