Where did the Blue WU pricing table go? I can’t find it anywhere in the docs or the blog post about WUs anymore
It looked like the below screen shot but was for each activity that is contributing to WU consumption
It was not a complete list as Bubble charges for things that were not on that list, but the items in the Bubble manual now are even less complete.
Anybody know where we can still access that blue table or where is there a 100% COMPLETE list of ALL activities that contribute to workload units? @fede.bubble do you know if that blue list has intentionally been removed and whether or not Bubble is publicly displaying somewhere the 100% complete list of ALL activities that contribute to WUs?
The stuff in the manual just doesn’t seem complete and has several items listed twice, which makes it even more confusing to reference
I’ve looked for that thing so many times and have only found it by searching Josh’s profile.
There’s no reason they should be forcing this update in October when they are still unprepared and leaving users in the dark on what they get charged for and providing us an almost unusable “logging” system to reference what we were charged for to optimize. Not that talking about it will change anything, they seem pretty firm on this one.
I’ll dig around a bit but I feel like the blue table you are talking about and the one in the Docs are the exact same? If anything, I would expect the one in the Docs to be more up to date than the one that was shared last year
alright @boston85719 quick follow up: what makes you believe the table in Docs is incomplete?
Also on the “duplicated” entries, notice the little bracket by those items, it’s trying to group them under Performing a database search" and “Lookup a specific item”
Hey Fede let me preface this by saying I ask this without any malicious intent, not knowing your background, are you a user of bubble from a platform perspective? (Ex: developed/monitored production apps)
I ask because not only myself but other members of the community have documented/posted many scenarios where math just doesn’t line up. Even when side by side comparing workflows, logs, network tab results with bubble WU documentation. There’s also many scenarios of simple workflows can be ran multiple times duplicated across multiple apps and produce different WU usages.
There’s also other scenarios where the bubble platform at its core just isn’t built to work with this WU pricing model and be effective, for example setting slugs like @code-escapee documented, where in reality something that should cost a couple WU end up costing many multiples higher per record.
I feel we’ve all accepted the WU model is here to stay, and honestly I’m personally okay with that, however I feel consistent, repeatable, documented usage/pricing with ALL of bubbles core actions being optimized to work with WU should be the bare minimum before forcing a community wide switch.
it’s been 1.5 yrs since the release if I’m not mistaken, at this point I feel these doubts and documented issues from the community shouldn’t be happening this close to everyone being forced off their grandfathered plans.
Thank you for that…you actually jogged my memory and I found the one that I saved also…same reason as you, the suspicion that it would disappear
Because they are. In the original blue pricing chart there were 19 items displayed, and that was not even a complete list…how do I know, because of uncovering charges that were not displayed and having Bubble support confirm that the charges are part of WU charges and are not listed publicly, such as the charge for ‘database trigger scan’.
In the documents there are still only 19 items if you do not count the duplicates, but there is also one item I’m not counting because the details are blank
I was trying to report to them the difference between costs of an aggregate search and looking up a specific item…couldn’t find those details anywhere, and the details of costs for looking up a specific item are not listed on the old blue sheet.
@fede.bubble Did somebody at Bubble indicate they are complete and that is all that is going to be provided?
The above is very poorly formatted…as expressed in this post, I thought the Lookup a Specific item was just missing details…now I just understand it is poorly formatted. The Lookup Specific Item should be bolded. The sheet should be separated and the last column for the ‘duplicated items’ should have a blue box with words Specific Item Lookup so as to be clearer and more understandable.
I would never have gotten to the point of knowing that those details are for looking up a specific item based on current format.
I was hoping so as well, especially since the pricing change is just around the corner.
I don’t believe there is a malicious intent to be misleading or not transparent…I think things have fallen through the cracks and not everything is listed. As mentioned the scan for database trigger change is not listed, nor do the documents talk about it, nor explain that we are charged the 0.05 WU for each database trigger scan that takes place, even if the app does not have a backend database trigger change for a particular data type…what that means, is every single time a data entry is created, modified or deleted, there is an additional charge (not listed) for a database trigger scan of 0.05 WUs; that is unless that has been changed and is no longer being charged, which would be ideal, or at the least the charge should only be incurred if the app has a database trigger change backend workflow for the data type that is created, modified or deleted.
They definitely procrastinated on getting those tools promised 17 months ago…
@fede.bubble my ultimate goal is just become fully aware of every thing that gets charged, so that I continue to do my best by my clients and the community at large with continuously providing helpful tips and tricks for optimizing apps around this new pricing scheme.
This started before I ever worked at Bubble I hope you can all understand that I don’t hold an encyclopedic reservoir of context-dependent knowledge (yet).
In my recent updating to try and ‘optimize’ my app I came across a couple other areas around WUs that I think have fallen through the cracks. This thread about referencing a repeating group was one area:
Also, there was something with client side filters which I thought would be performant or low WU cost, but actually Bubble moves the filter to the backend which then gets charged for. I know this likely makes the app more efficient and quicker, but since it actually costs more sometimes I would prefer it all be client side
yes, I am waiting on support on a similar topic as the post linked. If I have a repeating group and I reference the repeating groups list of things count there is a charge of 0.2 WUs, but If I have a repeating group that is a list of text or numbers, and I reference the repeating groups list count there is not a WU charge.
@boston85719 for the missing item in the Docs table compared to the blue table, I believe it just got renamed? In the blue table it said “Each data trigger workflow initiated” and in the Docs it says “Each backend database trigger event evaluated”.
Is that the one you were referring to? Or am I looking at the wrong row?
Remember when Bubble’s founders said they wanted to make pricing simple to understand and the reasoning for removing capacity was due to it not being clear what capacity meant for the majority of Bubble users .
The community should not be having to debug and find all usage of WU and make our own calculators based on what isn’t publicly available. It should all be in a public list which is up to date and it should be regularly looked at and optimized based on how Bubble is optimizing their system.
It is not the first time I have said it but non-transparency in this way just adds to the conspiracy that the WU metric gives Bubble absolutely zero incentive to optimize for their users. There should be absolute full transparency on this. Let people nerd out on the charts.
How long has it been since WU was announced and how close are we to the legacy pricing being over? Why does it feel like Bubble has just completely ignored / seen WU as an afterthought for all of this time? It simply hasn’t been handled well at all and sorry if you think this post is critical but whenever I speak with others in the community, this is the biggest drag everyone mentions.
The use of word evaluated in the new docs is much closer to what actually happens, however the explanation is not accurate from what support has reported
In the explanation it should include the fact that we are charged this not just whether or not the evaluation returns a yes or a no, but more accurately, whether or not a database trigger event even exists for the data type…unless, have they fixed this and made it work as people would expect and an evaluation only occurs if a database trigger exists for the data type that was created/modified or deleted?
let me preface this by saying I ask this without any malicious intent, not knowing your background, are you a user of bubble from a platform perspective? (Ex: developed/monitored production apps)
I hope you can all understand that I don’t hold an encyclopedic reservoir of context-dependent knowledge (yet).
thanks for your hard work helping bridge the gap especially when the community is being critical.
.
