It seems like the main issue is with Searches using the “contains” operator on a list field.
In some cases you can temporarily circumvent that constraint and instead use client-side advanced filtering.
It needs to be “Advanced Filtering” which will force bubble to run it client side, normal :filtering won’t work.
IE “Advanced: This DataType’s List Field contains X”
You can restore critical functionality to apps by using this trick
Seems like you don’t need to make and deploy any changes, I believe searches are back to loading now.
Same!
Back to normal here.
If it helps, I’ve been having this issue for at least 2 days now across multiple apps.
I’m also seeing the issue specifically with Do a search for queries, they don’t return any data, even though the database entries are definitely there.
As a test, I reversed the logic on some repeating groups by using Parent group's thing instead of a search… and the data showed up correctly.
So for now, it really seems like the problem only affects Do a search for (with or without constraints, I have both cases not working properly), and not when referencing data through parent elements.
Presumably this would have been an outage for enterprise customers as well. Can anyone please confirm?
@bubble Please share your post-mortem here when you’re ready.
The problem seems to be resolved on my end as well
Good point. I hope I don’t need to reestructure the main searches of my app, but it is a good solution for this bug. Lookslike it’s all set now, searches are performing as expected around here
@bubble What is the plan for regaining trust in stability? Wiping out vital parts of applications as an infra provider for 2h due to a regression is completely unacceptable.
Similarly, what is the plan for regaining trust in the status page? After so many outages not reflected on status, neither in a timely manner, nor updating historically as would be appropriate, it starts to seem like this page is a sales resource (“look how much uptime we have”) and not an engineering resource. This is not an appropriate communication strategy.
Is your app on an enterprise plan?
Completely agree with you. It’s obvious from the forum how many bugs and outages there are, while the status page stays almost empty. At this point, it feels less like a transparency tool and more like a sales argument (SLA always above 99% lol) and frankly, like a huge middle finger to all Bubble developers.
Don’t take me wrong I am huge fan of bubble but it just can’t continue this way.
The status page has lost all credibility. Just look at the “start time” of this outage, it was logged way after the beginning of the bugs.
This experience has been very frustrating. Since yesterday, our customers were reporting bugs. We checked the Status Page, saw no reported issues with Bubble, and assumed the problem was on our side. So we spent hours investigating, uninstalling plugins, rewriting flows… only to later discover that the problem was with Bubble all along. Now we’re stuck redoing everything we changed trying to “fix” it.
I’ve been a longtime Bubble user and often contribute here on the forum. I’ve learned to live with the platform’s frequent issues, even if not happily. But masking problems on the Status Page (likely for commercial reasons) feels unfair and harmful. It wasted our time, created unnecessary stress, and left us dealing with anxious customers — all because of a mistake on Bubble’s part.
And if you’re wondering why I didn’t open a ticket right away… well, I think we all know the answer to that.
verdade realmente frustante demais essa pagina de status, eu mesmo depois de alguns imprevisto tento sempre acompanhar pelo forum, pois sempre podemos contar com a colaboraçao das pessoas que sofrem do mesmo mal.
This is the primary reason my company is only spending $100’s per month on Bubble vs. $1,000’s.
Hi! Is anyone still experiencing this issue? I’m not being able to fetch data on backend workflow searches. I have a Growth plan.
Certain parts of my searches aren’t showing up. For example my Postmark ‘opened’ labels aren’t showing
same here my app are also taking forever to load. Whats happening to bubble? Platform has been very unstable lately. I cant even trust myself these days
I understand why you all would think this, but honestly the explanation is much simpler than some conspiracy to lie about our uptime: there are guidelines on when bugs need to be reflected as Status Page updates. And then it depends on a team member during incident response to go manually update the status page. Most of the time these rules work pretty well, but there are instances when we miss the mark like this week.
So what are we doing about it?
The team has been migrating processes over to Incident.io, including our status page. That means the automations we now use for dealing with SEV1, SEV2, etc issues will also automatically trigger status page updates that everyone will see.
Edit:
And you might be thinking “well but if you don’t trigger an incident then we are still screwed on visibility”. Correct. Team is also working on the internal guidelines on what qualifies to trigger incidents.
Quick tip for everyone: support team can also trigger incidents. If they get enough related bug reports within a small time window it will push an incident alert to engineering. That’s why it’s so important that everyone submit a bug report when something like this happens, it helps everyone.