Event condition not passed WU Cost

Hello,

When Backend Event Condition not passed. Does it cost WU?

When condition is not passed it means workflow does not execute or doesn’t run. And if it’s not run it can’t use any workload units. Question is if checking conditionals uses any WUs. :eyes:

The answer is it depends whether a conditional itself has to do a search in the DB. Like if a conditional is When Do A Search for all Cars :count > 20 this search will utilize some of the WUs.

But if conditional doesn’t call on backend at all then it won’t use any WUs. For example on an initial page load you might load number of all cars in a variable group. And now your conditional will look like this: When Var Group Number > 20. This won’t use any WUs cause the number of all cars has already been loaded in variable group.

Hope this makes sense.

PS be careful with loading Var Groups on page load. Unless you def. need them it might get out of the hand in terms of WU usage.

1 Like

What are Var Groups?

Group with data type that you use as a variable like a state, except dynamic

Yes.

When you schedule it, you incur 0.1 whether the workflow runs or not.

If your condition requires touching the database, which it most likely does if it’s a condition on a backend workflow, then you’ll incur WU for checking that condition.

1 Like

I thought so, just never knew there was a name for it. I just call mine Data.

Undocumented lingo won’t help new Bubblers.

There’s no set name for it. I use var - (name) which I think I picked up from Airdev’s apps.

I think I picked it up from Airdev too. They were the ones to introduce this concept.