Bubble editor incredibly buggy still

I honestly don’t know what to say anymore.

How are all these critical issues in the Bubble editor still being ignored by the dev team? It’s been weeks of dealing with broken and buggy core functionality in the editor, and the situation seems to be getting worse, not better.

I’m using the editor on vanilla Chrome, no plugins, on a high-performance machine (32GB RAM, i9 CPU). I’ve resolved the memory crashes, but now I’m faced with an editor that’s seriously degraded compared to just a few weeks ago. And no, I’m not referring to the new workflow builder — I’m talking about persistent, critical bugs that seem baked into the editor now.

Here are just a few examples - keep in mind that most of these only show up after working in the editor for a period of time (15 mins+ and you’ll start to see these bugs, although some also happen on fresh page loads randomly):

  • Navigation panel doesn’t update with new reusable elements or pages.
  • Reusable elements don’t appear in the element library.
  • Element tree often freezes, doesn’t render properly, or is totally unresponsive. Doesn’t highlight selected group.
  • Dragging elements in the tree is broken — items don’t land where they should, don’t appear, or appear randomly after multiple attempts.
  • Mapping logic fails to recognize inputs when data sources change.
  • Data source mapping sometimes requires weird workarounds like pasting values from elsewhere to be recognized.
  • Reuseables not displaying when added to the page builder they often have no preview
  • New API workflows don’t show up in the backend view.
  • Workflow folders get sorted alphabetically but don’t auto-scroll or highlight after creation, forcing manual searching to rename the folder you just created.
  • Element search broken intermittently, the search fails to return reusables by name. This also occurs in the navigation bar from time to time.

And that’s just a fraction of the issues. Many more have been listed in earlier posts by myself and others. The bugs are piling up faster than they’re being resolved, and it’s becoming incredibly disruptive to productivity and trust in the platform.

Yes, hard-refreshing the editor sometimes solves these issues temporarily — but expecting users to refresh every time they change a field, add a workflow, or create a new element is not a sustainable solution.

Please, Bubble team — these problems are not minor annoyances. They’re core functionality failures, and they’ve persisted for far too long.

14 Likes

1 Like

This one’s particularly annoying, requires a page refresh

2 Likes

Cc @Calypso_BubbleSupport

1 Like

I’m still finding so many bugs in bubble every single day…

Bug reports don’t go anywhere so I’ll post here as well.

Repeating group logic vs content is different

** this particular bug has plagued me for weeks. It seemed to only happen in certain places so I could never narrow it down and my assumption was always that bubbles underlying architecture was reliable (I should know better by now). The only way I was able to resolve this bug was by breaking it down into the most granular details and logging every step to narrow down the fault - only to find that my logic was correct and all the different solutions I had tried were likely correct also - it was just that the bubble editor was flawed and I had assumed it wasn’t.

Summary:

  1. logic shows first item as empty when it evaluates in the debugger
  2. data in the repeating group must remove empties from the list? and even though my reference is this repeating groups first item the logic still sees the empty item… so I had to add another filter to exclude empty items

Editor sidebar not clickable

chatbot is so slow…

please bring back a bug form! How anyone thinks this is an improvement on a simple form I don’t know. Before I could submit a bug in 15 seconds - this chatbot takes 60 seconds and is painfully slow for every message to be sent back.

If I’m frustrated enough to take the time and submit a bug report I shouldn’t be frustrated further by a chatbot that is painfully slow and makes it harder to submit a bug report. I just want to submit a bug and get back to building…

2 Likes

I don’t report bugs anymore because they took away the bug report form. BTW, I’ve experienced all bugs you mention, so I believe they are system wide.

4 Likes

I had stopped reporting bugs ever since they introduced the chatbot—it often feels like it’s there to deflect serious users from submitting real bug reports. Maybe that’s intentional?

That said, I’ve started reporting bugs again because many of these issues have persisted in the editor for months, and I’m honestly fed up with constantly having to work around them. I suspect others may have also given up reporting, so I’m starting this thread with two goals:

  1. Document and publicly list ongoing bugs — both to bring visibility and (hopefully) hold Bubble more accountable.
  2. Create a running log of submitted bug reports with timestamps — as a record to say: “I reported this six months ago and it’s still not fixed.”

My hope is that this transparent approach helps put more internal pressure on the team to prioritize these long-standing issues, rather than sweeping them under the rug.

2 Likes

I appreciate the effort. I sadly believe bubble doesn’t prioritize bug fixes any longer. If they did, they’d add back the bug report form…absolutely no reason there can not be a form and chatbot.

this is so true! and good luck managing more than one bug report.

check out this email from support. I have 6 bug reports submitted. how am i supposed to know which bug report this email is about?

can we at least add a thread to the bottom that show’s my original request.

2 Likes

thanks for sharing Mitch. I’ve shared the list internally and I’ll be asking some questions around next week to see what can be done.
Totally agree that the core experience needs to be 100% solid or otherwise it diminishes all of our features as a whole.

3 Likes

if you click the “our messenger” link in the email, the chat bot will open to the thread its related to. Additionally, in the bot, there is a “ticket” section displays the tickets that have been escalated to the specialized team and/or engineering.

Does that help?

I did get a response about the sidebar being non responsive - it is a known issue that the team are working on. I just wish it didn’t take 6-12 months for a simple bug to get resolved. I can’t imagine how many hours are wasted by devs reporting the same bug and support teams replying with “we’re working on it”.

The sidebar issue has been a bug in the editor for at least 2 months - possibly 3+. It’s a minor bug but all these minor bugs add up to major frustrations when you’re working in the editor all day and they detract from the overall great experience of bubble.

Thanks for the reply.

I know I’ve been quite critical of Bubble and its bugs, but I want to emphasize that I truly believe it’s an incredible platform overall. It’s just frustrating to see so many small yet impactful bugs persist—especially when they seem relatively simple and critical, and remain unresolved for months.

I really appreciate you escalating some of these issues. Hopefully, we can all get back to working in an editor we love, rather than feeling continuously frustrated by it.

1 Like

Thanks @fede.bubble. Exactly - the problem is how much additional friction that adds. Let’s say support replies with a question:

BEFORE:
I get an email with my orginal request (bug report) right in the email thread. I reply by email.

NOW:
I get an email with zero context or reference to my original request (bug report). So I have to:

  1. click a link to open a browser.
  2. login to bubble (very painful on mobile)
  3. wait for support chat bubble to load
  4. look through my tickets to find the recent bubble support chat
  5. scroll to my original request to finally understand which bug report bubble suport is talkign about.
  6. reply.

Including reference to the chat history (orginal bug report by me) in the email thrread would solve this. It’s how it used to be.

1 Like

bubble servers are extremely slow today

is bubble doing updates in asian timezone? it would be nice to know when the dev team plan to do big changes so I can plan around them…

I have noticed sundays seem to be a consistently bad day for bubble editor loading times - my up down is 300mbs and 4ms ping so I know it isn’t my connection.

Getting this error constantly today…

Not sure when this started but typing in the “arbitrary text” or “text” fields in the editor has been broken for a while. Constantly loses focus while you’re typing. Or, when you click on it, it highlights the whole block. Just very weird behavior.

2 Likes

That’s been a bug for a few months now.

Sometimes it highlights everything and then you start typing and oh crap I just overwrote everything…

Or you try to select focus somewhere and then it jumps somewhere else and you can really stuff up text/code. I stopped editing text in the editor months ago because it was so buggy and painful. Now I just copy paste from a scratch pad (notepad++)

1 Like

Bubble were definitely doing something on their servers that was consuming all the resources because now the editor is super zippy again…

I had even tested changing internet sources (mobile hotspot) and the issue was the same regardless and no other websites had issues (I also ran a speed test which confirmed all was good) - so it wasn’t my connection.

Just frustrating that I never know if I’m going to get a good day or a bad day in the editor. If I knew approximate downtimes I could plan around it at least.

right click on dynamic bug…

1 Like