As the title says, the custom event is returning the value “no” and it didn’t even run.
Unsure on the exact logic here, but it seems like you’d be able to just change your dependencies slightly to fix this.
maybe no is default, since workflow did not run and no result exists then the check can’t be yes. it shows as no unless the event is run and some tokens are found. If that is the case use something that allows an empty state or a type that is not binary.
1 Like