I can't sleep because of Bubble!

Bugs
1

You may have seen it; a few weeks ago, I opened the post below. There was a nonsensical WU increase in a customer application, and I spent days trying to prove that it was a bug. Finally, @Eram_BubbleSupport acknowledged that it was indeed a bug. However, after 3 weeks, it’s still under investigation.

I’m opening this thread because I’m now experiencing the same issue with another customer application. But this time, the problem is much bigger because this app normally consumes around 600k WU daily. So, the WU consumption due to the bug is significantly higher.

image
image1676×650 43.5 KB

It all started on Friday, October 11th, when I received a Sudden WU Spike notification. This is an app used by students, so the workload varies throughout the week. The usage decreases towards the weekend, as you can easily see in the chart. On Friday, October 11th, the WU consumption, which normally doesn’t exceed 600k on Fridays, shot up to 1M 683K.

I tried to figure out what was going on, and I found that a single “Make changes on a list” action in the “create-konu-soru” Scheduled Workflow event was consuming 89% of the WU.

I looked at earlier dates to see how much WU this action normally consumed. I discovered that the action, which typically consumed an average of 30 WU per run, had started consuming an average of 120 WU per run. Now, here’s the part that’s driving me crazy.

On October 12th, at 17:01, I completely removed this action. This action no longer exists in my app.

image

So, what happened next? Here’s the current chart for October 13th. Somehow, the Deleted Workflow Action is still running and continuing to consume a ton of WU.

image
image1206×750 70.2 KB

So, I ask you, what should I do in this situation? As I mentioned at the beginning of this post, I had already submitted a post and bug report for another app. Even though they acknowledged it was a bug, it took me days to prove it, and it’s still under investigation. That app was a small-scale one, so we only lost around $300, which is still not a small amount. However, this time, the app in question spends nearly $2000 monthly, and this bug will lead to much higher costs. Do I need to spend days of my time on every single case? Why is this system so buggy? Why is Bubble overcharging us? What would have happened if the app was even larger in scale?

What do you think? @Eram_BubbleSupport

5 Likes
2

And here’s where it gets even weirder:

After deleting the related action, I noticed that the WU consumption in the “Live” version normalized. However, the consumption was occurring in the “Development” version. The most illogical part is that this event isn’t even running once in the “Development” version. Even if it did, there’s no difference between the flow in the “Development” and “Live” versions. Ah Bubble, what is going on?

image
image1847×768 82.7 KB

image
image1838×575 28.1 KB

1 Like
3

I remember your previous post. Man this really stinks, more so because this is a bug that has been popping up here and there in the forum. Mostly from apps that switched from legacy to WU recently (from my own anecdotes).

Do you happen to have any other branches?

2 Likes
4

Normally, in the log, you should see the sequence running endlessly. I’ve experienced this twice in less than a week—once it was an unused button, and the other time a task kept running in an infinite loop. As I mentioned in another post, I had to suspend operations and then manually terminate them. It worked. The only logical explanation I’ve found so far is code corruption related to Bubble updates. This has happened before, and I had to go through all the damaged workflows.

Capture d’écran, le 2024-10-08 à 15.38.53
Capture d’écran, le 2024-10-08 à 15.38.531826×484 41.5 KB

4 Likes
5

Yeah my similar reported bug is still under too

3 Likes
6

This app did not come from a legacy plan. Actually, the old workflow existed in other branches, and maybe it can trigger something we are struggling to understand. I don’t know :confused:

7

Hello to everyone seeing this thread!

I’ve resolved my issue and would like to share how I did it. As I mentioned in the first two posts, nothing was working in the “Dev” version, the log tab was completely empty, and the Scheduler tab was the same. However, just as @JohnMark suggested, I stopped and canceled all the tasks in the “Dev” version. After doing this, the unnecessary consumption in the “Dev” version stopped. If you encounter this issue, I recommend starting with this solution.

Important note: This simple mistake cost me 2M WU consumption. Luckily, it was resolved before it could cost even more. This is a client application, and as a team, we work hard to keep our clients safe and maintain their trust in us. To this day, we haven’t missed a single deadline. However, due to the issues Bubble has caused with WU, our clients are being overcharged, and the development process is delayed as we need to report and resolve these problems. In this situation, how can I ensure that the client, who chose Bubble based on my recommendation, continues to trust us? This is extremely frustrating, and the technical team needs to address these bugs as soon as possible. @Eram_BubbleSupport

Thanks to everyone who contributed to this thread!

4 Likes
8

I’m so sorry to hear this. Have you had to remove any feature, or lost money because of this bug?

9

@fede.bubble

1 Like
10

Thanks for the ping.
I shared this with the team.

@Efe sounds like the support team already identified this as a bug but it hasn’t been fixed yet? Have you had any follow ups with Eram on your ticket, like asking for progress on fixing this?

11

Hey @fede.bubble, thanks for asking.

There are 2 different bugs. The first one is identified and under investigation. We’re keep contacting with @Eram_BubbleSupport for that case. But the bug related with this thread is new and I’ve created bug report.

I’m posting these bugs related to WU consumption here, aside from submitting a report, because this is one of the most critical issues—it can directly lead to significant overcharging. I’ve been wondering if I’m the only one experiencing these problems. If so, it might mean I’m not as good a developer as I thought. But if that’s not the case, then the Bubble technical team needs to prioritize this issue more.

However, whenever I post about WU consumption bugs, I notice other expert developers encountering the same problem, as seen in this thread. In fact, the Bubble technical team has already confirmed that a previous bug was indeed caused by Bubble. That’s why I’m quite certain that many app owners are unaware they’re being overcharged because of these bugs. So, I wonder, is the Bubble technical team giving this major issue extra priority, or are they just fixing it case by case for each app?

3 Likes
12

For me, it’s not costing money as it’s about 2 WU per day, but the time spent on trying to uncover the issue, debug, submit bug report, back and forth communication with support, has cost about 4 hours of my time.

7 Likes
13

This^^^ also it goes back to the way they are treating customers, when the community was irritated about WU in the first place they gave us the grandfather period to ensure it was a smooth roll out. Now everyone has been forcibly switched to WU and it’s still not documented the way it should be, there are still optimizations needed on bubbles side that we can’t control, and there are still bugs being found.

9 Likes
14

So what’s the bug related to? Scheduled workflows?

15

nobody knows.

16

Again, we are seeing this constantly, the WU approach means there is no incentive for Bubble to do what is right by its customers. Where is your credit for incorrect WU charges? If you multiply this by the size of the Bubble user base wouldn’t you have a class action for racketeering?

17

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