WU consommation from dev to live. A real problem

I’m continuing this thread : It finally happened, I missed something and used 7 million workload units in 24 hrs! - Bugs - Bubble Forum because something similar happened to me today. On a development version, a backend workflow consumed all my WUs within minutes.
I deleted the workflow, but the WUs kept decreasing.
My only option was to manually stop the overage.

I made a mistake — fair enough.
But it’s incomprehensible that my development site would consume the WUs from the live site. This should clearly be limited.

I’ve invested a lot in Bubble and recommended it to many companies. But this issue — the potentially uncontrollable consumption of WUs and the resulting exponential billing — is a major problem.
I’ve been working for some time now on migrating my data out of Bubble, and I’ll be finalizing this sooner than expected. Despite my initial enthusiasm for the concept and the tool, I’ll now seriously explore other solutions that avoid this kind of major inconvenience.

It’s been a year and a half since this thread started, and nothing concrete has been implemented to block these WU consumptions or protect customers. That’s truly unfortunate.

There’s already some stuff impletemented to prevent loop and issue like that!

You will find recursive protection and WU usage notifications

There’s no concept of dev vs live WU. Workload is for all your version.

Finally, if this happen once and you contact Bubble support, they will probably refund overcharge an help you to set protection against this to prevent this happening another time.

1 Like

The protections are there. You did not use them.

1 Like

Ok. But what exactly is your goal with this message? To make the Bubble community seem as unpleasant as possible?

Have you never made a mistake yourself?

Bubble itself states that some protections have been enabled by default since July 2024 for new accounts, but not for older ones (see: Bubble Docs)

I hadn’t seen that information.

And yes, many of Bubble’s clients are not seasoned developers. In fact, Bubble’s target audience is — and perhaps especially — small businesses like mine, which are able to build high-quality tools thanks to this platform.

Sorry, but if your comment isn’t meant to be informative and is only meant to be condescending, then I believe it would be better if you refrained from responding.
Thank you.

In OP’s defense, it’s a bit crap that we can’t set a maximum spend for a given app.

All i read was you putting the blame on Bubble for something that could have been prevented. Granted that you acknowledged you made a mistake, the rest of your original post contradicts your own failure.

Regardless of the size of your business, all investments should come with actions to minimize risk. In this case, when working with usage based pricing you should have seeked out preventive solutions and acted on it. I say this because it looks like you are aware that there are tools that Bubble have built in but did not act on it.

I make mistakes, I develop full stack and have all sorts of usage based pricing to juggle with. I will only blame myself for my failures to use the tools that are available to me.

Yeah. They really need to allow us to put some sort of cap. Be it in WU usage or dollars spent on excess.

This topic was automatically closed after 14 days. New replies are no longer allowed.