the whole time i just created each item per Line, instead of thinking about storing 50-100 Items as a List into a Cell which is amazing for Saving WUs.
When i tried to check the Condition if it costs more WU to check if certain Data is in the List the WU Usage is not much higher too.
Anyone who can also verify that?
In addition i tested to place the Condition on the Action and on The Event. What i found out that although my Condition consists of a Database Search No WU will be consumed, if the Condition is False. If that Condition is TRUE it Consumes WU.
For the Action weather the Condition is TRUE or FALSE in both Cases WU will be consumed.
You can checkout this spreadsheet of tests I performed with conditionals of various types and placed either on the event trigger or the action.
In my tests #14 and #15 I have the Do a Search for Condition on the Event Trigger. In Test #14 the condition would fail due to search constraints not matching completely, where as in test #15, the condition passes.
As such when the condition fails with do a search on the event trigger, you will not incur all the ‘individual data requests’ for any of the server side actions within the flow and will only be charged for the condition on the event trigger, but when the condition passes, you get hit with individual data request charges for any and all server side actions within the series of actions despite the fact that they do not have any conditions on them.
Then you can also see that even though the condition fails on test #14 my ‘Other Carges’ column shows I experienced
Search 0.30 for the condition in the search.
and my “Remarks” were
What is strange is the search charge of 0.3 was not charged in test 13 even though the same condition was used on the event. Only difference is user was not logged in on test 13, but that shouldn't matter since the condition is the same and should need to be ran in order to evaluate the search.
Then in test #15 my ‘other charges column’
Search 0.32 for the condition of do a search for user. Workflow of 3.66 that includes a Conditional Evaluation of 0.32, and 2.12 for create a new broker, but only 0.62 for the other two create a new things.
Which indicates we get charged twice for the evaluation of the condition, once in the very clearly labeled “conditional evaluation”, but also for the individual data requests.
I’ve been in a back and forth with Bubble support for a few months now to try and figure out where the bugs and issues are as Bubble support has expressed that the ‘individual data request’ charges are incurred as a result of evaluating the condition, but it has been difficult to express that the is another charge labeled as “conditional evaluation”.
So, it is difficult to verify what you experienced since it is drastically different from my experience.
Whenever the condition was placed onto the action, I was not charged when the condition failed in either test #16 or test #17, but was charged when it passed in test #18…what is difficult though is trying to understand that why, well this remark column on test #18
Strange that the create a new blog post section is 1.43 while the other two create a new thing were 1.12. Also strange that create a new broker was not charged at 2.12 has had been done in all other tests. Also strange that the 3 create a new thing were not charged the same amount. Strange that the 1.12 doesn’t add up to the normal 0.62 for create and 0.3 for search. Strange no conditional evaluation labeled at all. So very unexpected to see that 1.12 charged for create a new thing doesn’t amount to the same 0.92 that is expected if charged 0.62 for create and 0.3 for search as the condition. Overall very unexpected results, and wildly different than if the condition was placed on the event trigger.
@fede.bubble can you ask the team to explain the differences in experiences between users and charges for Do a search conditions placed onto actions versus event triggers
