Since I don’t have a 2nd brain cell, I shy away from using the Isn't live version is no. Wait, or is that isn't live version is yes when I want to run it only in production?
Well, you get he point. So I normally guard and route stuff based on App version is live . Today this workflow ran and I’m not understanding why. Any clues? Is my assumption about App version is live incorrect? Do I have a typo in live?
Here’s the message in Slack
Did you see this in the logs? What does it say?
Even if you had a typo, the App Version you should receive in the message would ALWAYS have to be “live.” There’s no other option, since the word “live,” with or without a typo, is part of your validation. It seems like a bug to me…
The only other option that crossed my mind is that this message is being triggered from another area of your app (perhaps forgotten? Or created to run a test?) with some other type of validation…
Have you tried using the search tool to check?
I’ve always had the same doubt, and to this day I don’t understand why Bubble inverted that expression, it would’ve been so much easier if it were simply “Is Live Version is yes” or “Is Live Version is no.”
However, your method using app version is live seems correct. I’ve used that approach in several apps myself, including cases where I needed to send data through the API Connector depending on the environment, and it has always worked perfectly, whether in live, test, or any other branch version.
The right thing to do would be to check the logs to see what might have happened, because your expression looks fine. Just to be sure, you can create a log item in the next step to record that expression’s value and confirm it’s coming through correctly, or look for it directly in the logs.
If it keeps failing, then it’s time to fire up the neuron fryer 
.
Result of step 1 (Cloudflare Action…)'s returned_an_error is yes and (Isn’t live version is no)
Isn’t live version is no = Live
Isn’t live version is yes = Dev
Thanks for all the ideas.
I checked, this was the only action sending that message.
I did the Bubble equivalent of unplug-and-plug-back-in by removing that condition and rewriting it from scratch. Same exact expression but now it guards properly.
