Retool app reverting on its own

App Building
1

The problem I'm having is that a Retool app that I've made changes to keeps reverting the next day and forgetting changes. This is happened twice now, where I have simply changed key/value pairs, then saved, and then ran it. I have even closed out Retool and returned to see that the changes were there, but then the next day the app reverted the key/value pairs to the original version generated by the automated app builder.

Am I missing a step after saving and running it?
What is a solution or something I am not doing?

2

I had the same issue but it suddenly stopped from happening when I started being a bit more diligent and not opening more than 1 browser tab that is in the edit mode… Lost a few hours of work but I definitely remember to pay attention next time. :smiley:

1 Like
3

Hi @DW_Ferrell I'm sorry to hear about this!

I agree with @ilmari that it could be caused by having the editor open in more than one tab. If multiple people are editing the app at the same time, that could also cause changes to be lost (the changes would overwrite each other). We are actively working on multi-player, which will resolve these types of issues soon

App saves happen automatically so you don't need to manually save, but if you are ever concerned about a save you can manually trigger a save by clicking command + s.

In general, Retool maintains a detailed history of app saves, but here are some actions I'd recommend if you see missing edits:

1). Check to see if Retool is experiencing an outage (We're not currently having an app saves outage)

2). Check the browser console for errors

3). Review the history in the UI for changes (in the left panel)

4). As a last resort, Step back in the recent history of your app to see if a past page save is working better. To use this history feature, append ?_historyOffset=5 (you can choose any number, but I'm using 5 as an example) to the end of your app url. This will allow you to "travel back in time" 5 page saves. You can increase the number to go further back in time if you still don't see what you're looking for. The idea here is to go back to the most recent working version (lowest # possible) so you don't have to redo as much work (going back 1000 steps would likely show data, but it could be many, many changes behind). ***WARNING!*** If you make any changes to the canvas when traveling back in time, that past version will become your present version and it messes with the history, so be careful not to touch anything! Once you find a version that isn't crashing and you'd like to make that your present version, then you can make an edit to the canvas (move a component, add a component, etc) to persist that view.

We also have a release management feature to have more control of the end user view for apps. Enterprise teams that need more extensive functionality beyond our release management feature, should consider using source control to manage their apps.

4

OK. Thankfully it has not reverted, and I have been mindful of only one window open at a time. Perhaps that was the issue, thank you!

1 Like