Just a few hours ago I replaced several “Do a search for” functions with a JavaScript script & database API. Is important to know up till a few hours ago I never ever used JavascripttoBubble plugin on my app and still in the workload usage dashboard it says this plugin used a lot of workloads in the past 30 days. It would have made sense if the workload usage would have been same as in the past 24h but it ain’t. Anyone can help me with an explanation why I see this discrepancy? Please see the screenshots bellow. Why the value for the past 30 days isn’t the same as the value in the past 24h since I implemented the javascripttobubble only a few hours ago?
Yeah… if this was implemented 24 hours ago, then the information is clearly wrong.
Have you opened a support ticket yet? I’m curious to hear their explanation for this.
These charts have always given me a lot of trouble when debugging. I was never really able to confidently match the information they show with the real-world scenarios in my apps.
At some point, I simply accepted that all of this is kind of a black box, and that I just had to trust the information being shown.
Oh, before I forget… why did you replace the searches with JavaScript?
Yea I did open a ticket and only got a BubbleBot reply to it. Nothing else till now and I have the feeling I will not get a reply. 
I have an admin dashboard where I show some values that requires a lot of DB interrogations in order to make some calculations and show them those values. According to the App Metrics displaying those values were triggering a huge workload usage so I wanted to cut off this usage by replacing the “Do a search” with a Get API call and JavaScript. I implemented this strategy on June 25. I just checked the metrics now and on the days following June 25 there is no workload usage for Javascripttobubble outputs so I don’t know what the heck they are measuring there and how they do it. In theory…having no workload usage for pulling those info out of DB using Get API call & JavaScript is what I expected to happen so I do not understand why on June 25 only a few hours after I made the changes I was getting those huge values.
Bubble’s “Workload Unit” system is a total money pit. On top of being expensive, we pay for it without really knowing how the charges are calculated.
I think those are reported as individual data requests without much further insight to drill down and see that those requests come from the JS output