Skip to main content

Why is my editor slow after merging branches?

After merging two versions of your app, the editor can be noticeably slow while Bubble loads and processes conflict data across the app. Performance improves once the post-merge calculations complete.

Written by Sofia Maconi

After merging two versions of your app — especially large apps or merges with many differences — the editor can be noticeably slow for a period. This happens because Bubble needs to load a large portion of your app to identify and display all potential conflicts, which is more resource-intensive than a normal editor load.

What you might notice

  • The editor takes much longer than usual to load after a merge

  • Pages and elements are slow to appear

  • Conflict markers take a long time to render or don't appear immediately

Workaround

Allow the editor some time to finish its post-merge calculations — performance improves once the process is complete. If conflicts are failing to load and you need to speed things up, you can temporarily append &issues_off=true to your editor URL. Note that this disables the issue checker, which is helpful for conflict resolution, so we recommend only using it as a short-term measure.

Did this answer your question?