Understanding Undo/Redo Functionality in Bubble
The Undo/Redo feature in Bubble is a useful tool for managing changes within your app’s editor, but it also comes with specific behaviors, limitations, and scope. This guide helps explain how Undo/Redo works, its persistence across sessions, and the types of changes it supports.
Overview of Undo/Redo in Bubble
Undo/Redo in Bubble allows you to reverse or reinstate recent changes made while building or editing your application. The feature is session-based, meaning its functionality is tied to the particular web session you are working in. Ending the web session also ends the history stored for Undo/Redo.
Scope: What Undo/Redo Can and Cannot Do
While Undo/Redo can reverse many changes, some actions within Bubble are not covered. These include:
Database changes
Plugin installations or uninstalls
Plan or subscription changes
Application deployments
Branch creation or deletion
For changes outside the scope of Undo/Redo, it’s recommended to use savepoints or version control for reliable tracking and rollback.
Persistence Across Sessions
Bubble’s Undo/Redo functionality retains some limited history across sessions, specifically:
Up to 50 undo items and 10 redo items are carried over after a page refresh or when reopening the editor.
This history is stored in local storage and depends on its availability. However, do not solely rely on this persistence for critical rollbacks, especially for large-scale edits. It is always safer to save your work and create defined savepoints.
Note on Technical Limitations
If you’ve cleared your local or session storage, Undo/Redo may seem to temporarily work due to browser cache retaining recent states. A full page refresh ensures the history resets entirely.
Tips for Effective Use
To maximize your use of Undo/Redo, consider the following:
Understand Its Scope: Recognize that Undo/Redo is not comprehensive. Use savepoints and version control for critical changes.
Be Aware of Persistence Limits: Refreshing or restarting a session may retain some history but should not be relied upon for major changes.
Plan for Exclusions: Always create savepoints before making database changes, deploying apps, or modifying branches to ensure these changes can be easily reviewed and managed.
For robust, long-term control over your application’s changes, combine Undo/Redo with Bubble’s savepoint and version control features.