WU bugs - overcharged

We need more community engagement on uncovering WU bugs

In one simple test, to verify if using recurring WFs is less costly than using schedule api workflow, I did a simple setup and test.

Setup below

  1. Simple recurring trigger - No Conditions

  1. Simple send email action - No conditions

  1. Simple Set recurring action

Please keep in mind for the following, there are no conditions on any of the actions or triggers in this simple setup/test

This is what the WU metrics shows as being charged for this

  1. Button click to set recurring action - Cost overall is 1.22 WUs for one run - this seems to be 0.62 more than it should be since, a button click trigger is not supposed to be charged, and there is only one actions, which should be only 0.6 WUs, and there is no indication in the charts that data retrieval (ie: individual data request took place, which, if it did should only cost 0.2 WUs) - so, where is 1.22 WUs coming from?

  1. Running the recurring Action overall shows 0.2 WUs for fetching data (the individual data request, which is correct) and the 1 run of the actual backend recurring which is listed as 1.24 WUs, which is strange as there is just one action (ie: send email) which should just be 0.6 WUs.


  1. Running the action shows evaluation of conditions (those conditions that are empty and do not exist so should not need to be evaluated)



Nowhere in the Bubble manual is there a reference to either conditions that do not exist, needing to be evaluated and therefore are charged, nor is there a section that details how recurring workflows are charged.

Based on the public details available, I would have expected to be charged only for the below plus the return of a individual data request and the data in terms of bytes…so something like 0.95 WUs, if conditions that do not exist even need to be evaluated, which they shouldn’t, so in reality, maybe 0.90 WUs, but not the 2.46 WUs the metrics show as having been charged.



@fede.bubble is Bubble devoting any of it’s own resources to uncovering bugs in the WUs other than relying on the user base to uncover and then notify of such?

Any other developers who can spare 10 minutes of their day to do the same simple test, can you confirm if you get the same results?

@Eram_BubbleSupport could you have the team look into this?

5 Likes

One thing is that you forget to calculate the fetching of Current user, but this if far from the difference that you have.

Will try to test later

2 Likes

I do not think I did, but believe Bubble did in the charts…that is the individual data request charged at 0.20 WUs I’ve included in the expected calculation…unless the ‘current user’ is not charged as an individual data request.

1 Like

Had to submit a bug report about this, as testing again today, I see another issue, which is that one first day of testing was charged only for 1 search, but on second day of testing was charged for 2 searches, even though nothing in the setup was changed.

I couldn’t imagine why it needed to fetch data two times on the second day of testing since it only needs to retrieve the current user at the time the recurring WF is set, or why it needed to search two times if the first day it only needed to search 1, although it could be that on first day of testing the chart was broken into two different bars, while on second day is was a single bar, so maybe the first day, the 2 searches were just split between the two bars…either way, still confused on why the seemingly overcharged amounts, and why there needs to be two searches to find the single item of current user in the one single place it is used as a dynamic expression…maybe we are charged for when we set the recurring WF and when the recurring WF runs?

1 Like

It is really complex to debug all these WUs for different scenarios and then apply learnings to optimise, test etc. Takes away a lot of time and energy.

We all have spoken so much about why the WU based system is quite faulty. There are bound to be bugs in this, but they still continue with this system.

After a point we all need to think of how we utilise our times as well. For me now Bubble is just a way to create MVP to test, iterate etc and not serious long term apps, because that’s what they want us to do. In my one app that I have seriously built, I have got locked in because it is way to complex and not easy for me to move out. But I wish I could.

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