WU pricing table

[boston85719]

@code-escapee

I suspected the list would disappear due to all the misleading numbers within so I saved it. Here you go.

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

@fede.bubble

quick follow up: what makes you believe the table in Docs is incomplete?

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 attempting to get that information to provide to a user on the forum who was having an issue with WU and optimizing their app for it. API Scheduling Contributing to 40% of Backend Workflow - #2 by boston85719

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?

@fede.bubble

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”

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.

@fede.bubble

If anything, I would expect the one in the Docs to be more up to date than the one that was shared last year

I was hoping so as well, especially since the pricing change is just around the corner.

@fede.bubble

Why would we do that? And what’s misleading? I can tell the team to review if there’s something wrong

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.

@chris.williamson1996

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.

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.