Why is the custom event returning "No" even though it didn't run?

bruhvat · 2024-11-03T08:37:46.991Z

As the title says, the custom event is returning the value “no” and it didn’t even run.

image1025×295 20.5 KB

Screenshot from 2024-11-03 11-28-571920×295 30.1 KB

ed19 · 2024-11-03T10:46:27.448Z

Unsure on the exact logic here, but it seems like you’d be able to just change your dependencies slightly to fix this.

hanan1 · 2024-11-03T12:11:09.418Z

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.

system · 2025-01-12T08:38:11.211Z

This topic was automatically closed after 70 days. New replies are no longer allowed.