That seems to be the case. I’ve been trying to get @josh to reply for a few months now about what he stated when WUs were first introduced regarding a needed feature to allow us to isolate which data fields to return when performing a search since we are charged per character, that adds up, and for some of the built in fields we likely do not need for a search result display to users, we are getting charged for something we do not actually want.
Oh but they do that already.
From support staff below
Our engineers have confirmed that data trigger checks, and their associated workload usage, are expected behavior. I’ve gone ahead and personally flagged to our Product team that this may not be clearly indicated in our documentation as you mentioned. We truly appreciate you flagging this to us as it helps us ensure that we are as user-transparent as possible!
To answer your questions, the expected WU expenditure of a data trigger scan would be about 0.5 WU plus whatever WU is needed to evaluate the condition (e.g., if it queried some data to evaluate the condition, it will take additional WU). This data trigger scan will be done whenever changes are made to the database even if there is no database trigger change associated with the data type that was changed.
My apologies, the amount should be 0.05, not 0.5 WU which was a typo on my part
So, there is no public disclosure on the cost sheet about a 0.05 WU consumption for a database trigger scan when we create, modify or delete a data type that doesn’t even have an associated database trigger event in the app.
If engineering is able to confirm that the charges incurred for database trigger scans is expected behavior, why do users need to submit bug reports about them to have a support agent flag the fact it is not listed and that Bubble is failing on the user-transparency they state they are striving toward; why wouldn’t they just sit down with engineering and say “What all incurs WUs and how much WUs?” and then just make the list to be inclusive and exhaustive of ALL things that incur WU costs? @payam.azadi
I imagine you are correct, that they are checking every single record of the data type to see if the slug value already exists, since it needs to be unique, they need to ‘scan’ all to check for uniqueness. And I imagine that they likely have no incentive to optimize that, so likely every single field value is returned for every single record that is getting checked against which means there is also the 0.000003 WU for each character returned for each data field for each record.
If they are checking against all records, but are not returning all data fields and have optimized it to only check for the slug value of each record, then Bubble should be putting that feature into the editor so we can eliminate the return of field values we do not require for a search, something @josh stated was on the list, but maybe somebody scratched it off.
They would have been smart to focus on performance and stability before jumping into the whole AI craze…HEY LOOK A BIRD!