WU Conditional Evaluation

boston85719 · 2024-10-27T04:06:44.940Z

Is anybody else getting charged 0.64 or 0.63 WUs for evaluating if a condition exists on a backend workflow action or not?

Reply from support attempting to address concerns of mine from this post.

The “Condition evaluation” component refers to the necessity to evaluate whether a workflow has a condition.

Note, this is not a cost of evaluating the condition as the action has no condition. This is expressed by support as a cost of evaluating if a condition exists or not.

Additionally, would anybody expect that is charge of evaluating if a condition exists or not to only be applied to backend workflow actions and not all workflow actions? Seems crazy that it would only be applied for backend workflow actions, as the WU metrics in app do not show this charge for any client side workflow actions.

chris.williamson1996 · 2024-10-27T04:18:31.969Z

boston85719:

Additionally, would anybody expect that is charge of evaluating if a condition exists or not to only be applied to backend workflow actions and not all workflow actions?

I’d expect any and every possible charge to be documented in the WU documentation pricing breakdown which again it doesn’t appear to be. Which they keep claiming everything is documented up until a new one pops up and support seems to know about it but the public doesn’t.

manual.bubble.io

Activity types | Bubble Docs

This section covers how different activity types contribute to your app's total workload

There is no possible part of pricing we shouldn’t be aware of and it does seem that they keep popping up and new bugs keep getting found.

ihsanzainal84 · 2024-10-27T04:46:01.955Z

Does this include the 0.6 from running a server side action? Or is it 0.6 + 0.63?

boston85719 · 2024-10-27T09:42:36.921Z

Server side action is 0.6; the evaluation of if a condition exists of 0.64/0.63 is in addition, so 0.6+0.64=1.24 total to run one server side action with no condition.

boston85719 · 2024-10-27T09:43:23.196Z

That is why it’s confusing. If it’s not documented it seems like a bug.

georgecollier · 2024-10-27T10:48:07.200Z

boston85719:

The “Condition evaluation” component refers to the necessity to evaluate whether a workflow has a condition.

I think support is wrong. We aren’t (supposed to be) charged WU to check if a condition exists or not, with the exception of backend triggers where every time a Thing is changed, you’re charged 0.05 WU for every trigger with a condition on that datatype. We are of course charged WU for the expression on the condition.

If support is right, then you are also certainly right that it is not documented but should be.

boston85719 · 2024-10-27T10:59:36.417Z

If support is wrong, it means there is another bug charging more WU than it should.