Gentlemen got very strange WU consumption spikes, since may 18 see this daily in my apps on different accounts. Same workflow “Deleted workflow: web”
Anyone else noticed?
Yup. I see the same thing. But I don’t claim to know how to read any of these graphs or what it means.
I think you deleted some workflow, but Bubble still needs how many WU that workflow consumed, so it says it’s just a deleted workflow.
The same thing happens when you delete something in the database and it has relations with other data types; the field shows “deleted thing”.
That makes sense. Like earlier in the month there might have been a frequently run workflow but now it’s gone, so Bubble just calls it a deleted workflow.
Doesn’t makes any sense to me…
In one app I had no changes for two weeks, but found it even there.
stablr and predictable consumption week by week and then spike with deleted workflow
I deleted a data query, it’s been two days, and the bubble shows the deleted workflow graph daily, before it only showed it in the month, when we deleted something, now it’s showing it daily, even when deleted, could it be counting since they’re not using it, is it a bug?
So I’m starting to transfer my database to Supabase
This is a big concern. I hope someone can get to the bottom of it. Bubble is expensive enough without phantom WUs
Ask support
Check out my plugin
It can save 99%+ workload units on bulk creation of data and 95% on fetching data, as well as improving content download speeds by 30-50% on average…there are tons of other useful features that make building apps that are more modular, powerful and easier to maintain. Plus opens doors for features like database backups and robust changelogs.
Why? If it is just because of costs of WUs, it is not necessary with the Hybrid Data Structuring approach my plugin enables users to implement into their bubble apps with ease.
That is correct, and if you look at the graph for previous time periods where the workflow had not yet been deleted, it will show still in the graph as ‘deleted workflow’ since the graphs only pickup from Bubble what is the current name of the workflow or search, so if it is deleted all graph references, even for past time periods will show it as deleted.
The above in regards to looking at past time periods when the workflow had not yet been deleted would explain why it shows during those no changed 2 weeks the ‘deleted workflow’
Do you recall where that workflow was or what it did? If it is perhaps part of something else, like it is on a specific page, you can cross reference page loads for that page to see if there was a spike there that could help account for the spike in WUs for the ‘deleted’ workflow.
In the end, it is a known fact that there are bugs in Bubble workload unit metrics, tracking and charges. There have been at least 3 publicly announced this year regarding workload units being charged many multiples more than they were supposed to, and any app owner who reported it as affecting their apps were reimbursed, but anybody that maybe encountered it but unaware and so therefore did not report it, were not reimbursed.
So, if you see something as unexplainable, I recommend taking the same approach that I do and call on Bubble support to attempt to explain it. They usually do a decent job of twisting words to make it seem like a non-issue or they answer completely different questions so as to avoid answering the questions directly. But personally, I have given up on Bubble support to be able to accurately diagnose and troubleshoot issues regarding WUs and their inaccurate and unpredictable and buggy logging of consumption. However, in a situation like this, where you are experiencing a spike that does cost you, I would reach out to support to report it.
I am seeing the same thing on one of my apps. I think I am encouraged that others are getting this and not something wrong specifically with my app. But I would like to know what is going on here. To my knowledge (as the only dev on the app) there hasn’t been a deleted workflow but I am seeing that this deleted workflow was run 992 times TODAY. It isn’t a concerning number of WU but more concerned that something is happening on my app that shouldn’t be.
have it in my apps too! What is this @fede.bubble what is going on with these workload unit charges?
@fede.bubble I see this in the two apps I’ve looked at so far
I sent an email to support about this as well, but this seems like a system wide issue that is at the very least, causing confusion for people.
edit
I’m batting 1000% here, 3 for 3
My expectation is that these are not necessarily WU charges we are not supposed to be incurring, but a bug in the workload unit charts (the forgotten about step child of Bubble) that are not allowing it to properly pick up which workflow as clicking onto the chart does nothing.
edit
Okay, so this looks like Bubble is trying to update their workload units in order to separate between web and mobile and in this have not completed the task before rolling it out. Can see in network tab just the simple use of ‘web’ as the tag on the workflows. So somewhere it was maybe not bringing in some nested objects which would be the list of all workflows ran, and instead just groups them all together.
This I hope is not going to be the new normal and that Bubble will be fixing the feature to be more in line with previous feature of actually seeing a breakdown of individual workflows rather than just a grouping since clearly just a grouping does nothing to help us if trying to track, analyze and optimize for workload units.
1 Like
Response from Bubble Support
Regarding your inquiry, we discovered a bug where a system-generated tag (usually labeled as “web” or occasionally “mobile”) unintentionally overrode the tags we normally use to track workflow-level and action-level WU (workload unit) usage. While the workload unit usage was consumed, it was not attributed to the workflows/actions from which they were originally consumed.
As a result, during the time this bug was active, usage data for individual workflows and workflow actions wasn’t recorded as expected. This means you won’t be able to view WU usage broken down by workflow or action for that period.
This does not affect billing in any way, the volume of usage remains the same – only what you see in your app’s workload charts. The incorrect tags will remain in the data for now, so they may continue to show up in your usage views until 30 days have passed since the last time that “Deleted workflow: web” or “Deleted workflow: mobile” was attributed to any workload unit usage.
2 Likes