Emails are still sending out 24+ hrs after spikes happen. Pretty counter intuitive as we are already charged at that point.
Can we get the heavily requested webhooks yet so we at least have an option to manage our own alerts instead of being reliant on bubbles delayed system?
Support advised me in February they’d be fixing it in the “next update” as it was too big of an issue to quick fix. (Obviously hasn’t happened)
We are 5 mo away from all apps being forced onto a bugged out pricing system 
Check your DM’s! 
We’ll release next week a tool to get WU spike webhooks.
Free and without sign-up.
As we’re wrapping up the development I’m wondering if anyone has specific use cases or needs in mind?
For example set the spike trigger,…
Bubble is stupid in that it’ll send spike notifications even if it’s a test app that’s using 300 WUs a day, so the day you develop on it and use 2,000 WUs you get the notifications/error message! I’ll probably stick it out for Bubble to fix it but if you’re doing it then a minimum WU threshold and a % in X time threshold would make sense.
I’m still trying to wrap my head around the WU pricing.
It all seems pretty complicated to me…
then again I’m new to Bubble and still learning.
It seems most software programs charge based on the number of customers. 500 = 250, 1000 = 300 etc.
I understand one app with 100 customers may use more WUs than an app with 500 customers depending on what the app is used for…
but I’m still trying to figure out how to estimate how much an app would cost to operate monthly.
How or what would you tell a client if you were building an app for them in Bubble?
Maybe I’m overlooking something here, but the whole pricing thing in Bubble seems like one of the most complicated when it comes to figuring out pricing?
Unfortunately we can’t, you can take the exact same app concept built 2 different ways that cost vastly different amounts to run each month.
Unfortunately being a good bubble developer doesn’t mean just knowing how to build correctly in bubble anymore. With WU now it means knowing when and where to make your client sacrifice either money, scalability, or speed to help their business at the stage it’s in.
It’s not as big of a deal on traditional code bases because essentially what bubble has done is taken processing and data storage and marked it up a few hundred or a few thousand percent depending what actions are happening.
At the beginning I didn’t like the new pricing model but I advocated for it people because businesses need to learn to adapt or die but it’s been over a year since its release and they are still finding bugs in the pricing model, support makes the bugs out to be your fault and allows you to use your “one time forgiveness” on WU charges, and we just keep continuing down this path where in 5 months everyone will be moved off legacy onto the new plans which consistently find bugs and failures to notify. Then we are given expectations of fixes around how we are being charged just for the expectations to be blatantly missed.
Also…documentation is clearly missing some actions that incur WU so no where are we told we are being charged for something up until you ask support and find out there’s hidden undocumented charges
AI & mobile app functionality etc is their priority over a broken pricing system and uptime though 
Thank you for your reply.
I’ve been working on an app…slowly but surely while I’m learning Bubble. Bubble has a lot of great features.
The WU thing is still confusing though. It boggles my mind to understand how they came up with using that as a pricing guide when it’s so hard to figure out.
I do enjoy reading your comments. I can tell you know a whole lot about what you’re talking about.
