I cannot understand how adding one thing to a list of things is costing me 15 work units. I checked and I don’t have any database triggers running on this data type. Please help!
FYI:
User Extended is my satellite datatype that is linked to each User to store extra data. This datatype has a field which is a list of Interest Lists.
Interest List is a data type with about 10 fields of mainly structured data except for the description which is rich text.
Other parts of my app are doing similar operations but incur about 1/10th this many WUs.
I am also charged about the same amount when removing the item from the list. If this is normal, that’s fine and I’ll just re-work my app to not use lists.
The problem is how Bubble work with a field that is list of thing. I’m not sure, But I guess Bubble may retrieve all items in the list to add (or remove) one item (based on the racing issue with SAWOL and how this work). This could explain a higher WU usage than expected. This is the kind of improvment Bubble need to work on. However, 15 seem very high…
Laura left too? I just became aware that Alan left recently.
@chuckyte its likely pulling all user information and all of the user extended information. Thanks for posting this, we need more users highlighting these types of issues as even if it pulled all information, the 15WU is excessive and likely due to a bug on top of inefficient code by bubble.
@chuckyte if you haven’t already I would suggest opening a ticket with support they can look into your app. Just follow the chatbot instructions: Bubble Support Center
The crazy part of this is that this is happening on my test version which usually has nothing in the field (list of Interest Lists), so retrieving the list before adding should not incur much WU since there is nothing in the list to begin with.
Thanks to everyone on this thread. I’ll post this as a ticket and let you all know the result. Hopefully this is just a simple error on my part (which is usually the case), but we’ll see…
I’m in communication with someone from the support team. Meanwhile, I’ve got other workflows that have not been touching in a long time that are now also completely out of whack. Like an API workflow to send an email-- 36 WUs! This is crazy –
Inside User Extended datatype, there was a field that was a list of images. For certain power users this list will getting to be 10-20 images.
So what I didn’t realize, was that by adding something to a list in another filed within that datatype, it seemed to be pulling the list of images in another field (that field is is not referenced in the action) in that datatype.
I haven’t fully wrapped my head around the implications of this realization.
Unless protected by privacy rules fields will get loaded. It’s one of the reasons I stopped storing images as lists and store their URLS (as text) instead.
