We are unable to use and edit some of our applications. Not all applications are affected.
We've not modified them for some time.
Goal: End users be able to use apps. Developers be able to edit apps.
Steps: We've already tried to revert previous version of the affected apps (which doesn't seem to work). We've also tried to unpublish and republish the applications.
Steps to reproduce: View or Edit an affected application. See, that the page is empty. In the Edit mode there's no components visible.
Details: When I compare changes (Current Version vs one behind) it looks like all the code in the Current Version has been reset as if it was a new application.
Addition information: We use cloud version (3.186.0).
We are also seeing this issue for:
app uuid: da6cfe5e-225d-11ee-ad59-9f7a1f3a8836
app org: hearthdisplay
The error we are seeing in the console is: Uncaught (in promise) TypeError: te.toObject is not a function
The app state doesn't load at all, and duplicate the app also results in an empty application. It's not loading at all and reverting in any capacity does not work.
Hey folks! Following up to let you know that our engineering team has identified the root cause and reverted the offending change. The issue resulted from a change in how app styles are serialized which, in selective circumstances, resulted in Retool serializing and persisting an empty application state. Our engineering team is working to identify and correctly populate all history entries with erroneously empty states. This will take some more time, but you should now be able to revert your apps to recover a functioning state from a prior history entry.
@jadetools for app da6cfe5e-225d-11ee-ad59-9f7a1f3a8836 reverting to the last history entry, dated 2025-03-27T17:19:53.647Z, should restore your app to it's previous functioning state. But let me know if you're seeing otherwise!
@J_Peach reverting to a recent previous history entry should restore your app to a functioning state. If you can share the uuid(s) of your impacted app(s), then I can share the specific history entry to target, just let me know!
@J_Peach I had to revert only the one application I tried to recover yesterday. The rest of them did not require any actions - they started working.
Everything is working now.
I had to revert only the one application I tried to recover yesterday. The rest of them did not require any actions - they started working.
Excellent news and thanks for sharing those details! To clarify my previous message, the issue was broadly causing applications to fail to render and, in some cases, also could have persisted an empty state in your history entries if a page save occurred while the app was in a broken state. Apps where an empty state was not persisted should be functioning now without any action. Apps where an empty state was persisted will need to be reverted to a prior history entry, which should be possible now that the underlying issue has been remediated.
