I've encountered multiple cases where I assumed my changes were saved, but when I reloaded the page, they were gone.
This happens every so often and I'm not sure what causes this to happen. For the record: I am not doing anything out of the ordinary.
Anyway, I think having a button in the top-right corner to allow users to manually press Save would provide a safer way to ensure any changes are saved.
This button could be triggered automatically each time a change is made, or a label that says something along the lines of "Last change was made at [timestamp]".
I've had to redo some of my work because of this issue and it's very frustrating.
It can definitely feel like a bug (as this post is tagged) when the autosave isn't fast enough — sometimes it's snappy, other times I found it can be 5+ seconds. Probably a bunch of factors involved.
That said, there is a manual way to save: via shortcut! Cmd + S on Macs, but probably similar on other platforms.
I find this handy when I need to use "Compare changes" or create a new release without artificially waiting around an indeterminate amount of time.
In that case I would expect there to be some alert asking me if I want to close my window if any changes haven't yet been saved on your end.
While a delay might cause the issue, the user is unaware of this happening. Besides, network difficulties might also be the culprit.
I think, ideally, there is some information in the top-right corner showing the last time it was saved. And possibly even a toggle to turn auto save on or off - in case of the latter, a button is provided to manually allow users to save their work.
This last part could actually be helpful if you don't want your changes to be saved, for instance when trying out something new or running some experiment.
Hi @emozio, I'm sorry you've been experiencing loss of progress in your applications. We are currently investigating the root cause of this issue in order to fix it for good.
Ideally, our changes would be saved automatically and we wouldn't need to manually save them. However, we've seen that this is not working perfectly right now.
It seems to be related to Retool migrations, if you open the History tab and restore your app to the save before the latest migration, you'll recover the state of the app and will able to make changes that get saved.
This is not a great experience and I'm sorry for asking for this extra work whenever this issue presents itself. That being said, you do provide a great alternative, I've extended this feedback internally. Thank you for sharing!
In case you would like to see the full report of this incident:
Hope this helps clarify my vision. 