Why Pay for a Bug We Didn't Cause? This post contains a high amount of WU

Why pay for a bug we didn’t cause?

The Hero Icon Plugin was interfering with the RG’s condition.

Here’s the thing… you did cause this bug by installing a third-party plugin and not detecting or diagnosing a problem in how it worked. Bubble is a programming language. Programming languages are complex and can behave unexpectedly. The burden is on the developer to build an app that works, and to verify that third-party tools don’t cause problems.

If Bubble had somehow fundamentally broken the way Bubble operates, that would be an entirely different issue: you have a right to expect the system to behave consistently.

I’d argue changing the pricing structure to WUs has fundamentally broken the way Bubble operates.

2 Likes

thanks for the update.

since a lot of successful apps on bubble do use plugins (public or private) it’s surprising not to have a proper postmortem about this bug that could affect any other plugin.

1 Like

Since I have experienced a development on this side, I wanted to share it with you. I received a surprise email from the Bubble support team. They refunded the excess WU consumption during the bug report process and issued a refund for my invoice regarding this. Although they stated that this was an exceptional case, it is good news.

First of all, this is definitely the behavior I expected. It keeps the reliability of this platform and the team stable, and even increases it. I hope they take a look at the ideas and comments above and implement potential improvements for a better experience.

1 Like

I’m glad they did the right thing and not what some other users on this thread were advocating for or attempting to rationalize. Thanks for the update.

1 Like