@daas @ZeroqodeSupport
I am not using this plugin and with the first answer I received from the support team yesterday I am pretty sure there is a general problem in bubble at the moment.
Hi all - Laura from product jumping in; I can definitely appreciate that there’s a lot to dig into and we don’t always make it as easy as we could (something my team is working on, piece by piece!). I wanted to let you know that we are investigating an issue where WU calculations may be incorrect for references to searches that have already been executed – the examples shared above are really helpful to see. Please (if you haven’t already) get in touch with our support team so our engineering team can have specific examples to look at as they are investigating. I’ll be sure to update here when we have a fix rolled out (or a substantive update).
Hey Laura !
Thanks for the update.
Any ETA for a fix on this issue ? My app is consuming a lot of WU. I have to paid for a first tier of overages, but it probably won’t be sufficient…
Pretty sure I’m not the only one in this situation ?
Anything we can do ?
We are taking a look now and hope to have a fix out in our next sprint. If this is having a significant impact on your app right now (not just a few dozen WU but it’s causing your plan to get to a place where you’d need overages, etc) please reach out to our success team to talk about what options there are.
Hi Laura, do you have an update?
Hello everyone,
I trust this message finds you well 
Our team has thoroughly investigated the recent concerns regarding the Fuzzy Search plugin. We discovered that it was consuming more workload units (WUs) than anticipated. In response, we have released version 1.26.0. This update enhances efficiency by reducing WU usage.
For those who have experienced this issue while using our plugin, we strongly recommend updating to the latest version. Following the update, please monitor your usage over the next few days. Your feedback is crucial for us and we would greatly appreciate any reports on whether the usage spikes persist.
Wishing everyone a productive Monday 
I’ve come to the same problem, and all of sudden the cost of the apps went up, wich makes me question if the platform is safe for developing new projects, given that it seems that each month there’s a new problem on it
Just to drop by to say this problem has not yet been fixed.
15 days now it’s caused me to be heavily into WU oversages fees.
Slightly concerned at the moment.
Hey @asked111 !
Nope, they still haven’t fixed it…
Support told me that they are trying to fix it by the end of their sprint (i.e end of january).
They assured that I won’t be billed for the WU Overage caused by this issue.
I suggest you contact the support and really make sure that you are « in their files » so that they don’t bill you for this.
There is a clearly an issue and they are aware of it.
I’m sure they won’t let us down on this, I have faith in Bubble 
That plugin shouldn’t be used for large amounts of data. At all. Please use algolia. There’s a free plugin (it’s mine) and you can be set up in hours.
Stop using the fuzzy search plugin.
Well, this plugin is very convenient, which us why I was using it.
I have only around 200 records to search in…
I now have switched to Algolia, but it’s way less practical
Why blame Bubble for an issue with a plugin that you continue to use? You can still rack up costs with bad plugins/libraries in native app development.
I never said I used the plugin, the WU increased in all my searches in different apps without this plugin.
The issue isn’t with the plugin.
Yes, Fuzzy Searches tend to consume a high amount of WU, but in this cass is with Bubble.
If you take a look at the previous essage of this thread, you will an answer for a member of the product team; saying that they are searching for solutions.
Ah my bad. I thought you were using the plugin.
No problem! Just hope they fix it and we don’t have to pay anything more
Hi Laura! I’ve already sent a bug report but didn’t receive any news from the team, anyway Bubble is not going to charge users for this increase, right?
Just an update on this one in case anyone else suffering from it. Got this reply from support:
“For the WU problem, it seems like our engineers are close to a fix on this, so we’ll get back in touch you with once this is confirmed! Thank you for your ongoing patience there, as it proved to be a bit complex of a behavior to solve.”
Cheers
Greetings,
My name is TJ, an engineering manager at Bubble for both our AI and Scale teams. I would like to give an update to this issue on the WU spike in January. A regression in an optimization we made for real-time updates caused the client-side code to do more redundant work than necessary regarding searches / search invalidations. This regression is what caused an increase in workload units for some customers in January.
Here are the answers to some questions you probably have:
Q: When did it get resolved?
A: The regression was pushed on the morning of January 2, and it was resolved around 11:50 AM ET on Feb 8 for the main cluster, and 9 AM ET on Feb 9 for the scheduled cluster. However, it may have taken some time after this for it to fully resolve on your WU charts since the fix wouldn’t affect the sessions of any end-users who already had an active connection with your app when it was deployed.
Q: Why did we make the original optimization?
A: We are working to help Bubble apps scale significantly. To that end, this fix was intended to reduce inefficiencies with how our servers handle real-time updates.
Q: Why did it take so long from initial reports to resolve the problem?
A: There were a couple of reasons that caused this delay in both identification of the issue and resolution:
- Our initial hypothesis was that this was related to a previous bug report we received in November related to searches in repeating groups (this post). While that turned out to be unrelated, our investigation down that path did cause us to miss the regression that happened on January 2.
- Our process now alerts us more efficiently, allowing us to quickly resolve issues and improve real-time updates and WU cost monitoring.
- As Bubble grows, we are still building out real-time observability tools to alert us to anomalous behavior. While we do have observability around WU, in this case we didn’t have alerting around real-time search WU costs.
- For this point, we are prioritizing WU observability and testing for more of our end-to-end flows.
- Our goal is to significantly improve the scalability of our data operations, allowing your apps to manipulate millions of things instead of just tens of thousands. To achieve this, we must make significant changes on our end. These changes will ultimately result in more efficient scaling for your app without an increase in spend on your side.
Q: What is Bubble going to do to refund / credit our WU due to this mistake?
A: We want to make it right as this was our mistake. If you’ve seen an unexpected increase in workload usage in your app since January and believe it may be related, please visit the Support center to get in touch with a member of our Support team. Simply open the AI-powered chatbot, ask to talk to a person, and provide the details of your situation (including a link to your app editor and a reference to this forum post) to ensure your question is routed to the right team.
–TJ Andrews