Question about 11/30/18 release (When the condition evaluates to no, other properties aren’t calculated)

Questions
1

Just saw this release note, which doesn’t include any further detail:

11/30/18 | Workflow engine improvements: when the condition evaluates to no, other properties aren’t calculated.

Wondering if this release fixes a long-standing frustrating issue that I’ve had to go through many hoops to work around in the past, which is that when Action Conditions (“Only when …”) evaluate to no, they don’t stop “Get data from an external API” calls from running: Can someone @bubble please confirm? Or can you clarify what you mean by “other properties aren’t calculated”?

I tried a simple test, and I feel like this may finally be resolved with this feature release (yay!), but it’s too much work to try to re-create my original use case to know for sure.

2

See this post:

3

Perfect. Thanks, @dan1! Missed that thread. Mishav’s question and Emmanuel’s answer were exactly what I meant and exactly what I was hoping to hear! -Ed

1 Like
4

Hello, I realize this is a very old post, but do you know if this was, in fact, fixed? I have a similar case (“only when” condition is no, but when yes, it should make an API call and stuff some value into a state). I’m finding that even when the condition is no, the API call still goes through, even if the resultant value doesn’t get stuffed into the state. So the result is correct, but it’s making extra unnecessary API calls.
Thank you