Field is being filtered as if it's empty (it's not)

Question

Hey all, we have a Zap that is meant to synchronize user credentials between a scheduling and reservation system (WellnessLiving) and Discord. Whenever someone cancels their membership on WellnessLiving, Zapier receives their profile data (this is the trigger). There’s then a filter that checks to see if the user’s profile includes a Discord username--if this data doesn’t exist, the filter stops the Zap.

The issue we are having is that even when this field has data, the Zap stops at this filter. I’m not sure how to resolve this. See screenshots below:

Data for a recently stopped Zap run. The filter checks to see if data exists in A Custom Field 1412294 Text Value

The configuration settings for the filter.

SamB · Accepted Answer

Hi​@waystone1736!👋I did some checking and found a bug report that matches this issue where Filter aren’tseeing the mapped field values when the exists/doesn't exist conditions are used.Can’t make any promises around when it’ll be fixed, but I’ve added you to the list of folks being affected so you’ll get an email notification from us once it is.For now, since the Filter ischeckingto see if a specific field value exists perhaps you could add a Formatter (Text > Default Value) action to check if that field contains a value and if it doesn’t, output the words “No Value” for example. Then updatethe Filter condition to check the output of that Formatter action instead, only allowing it to continue if it(Text) Does not exactly match the value of No Value. Since that approach wouldn’t use the affected exists/doesn't existconditions that may help to get the Zap working in the meantime.Let me know how that goes if you give it a try!

Fahad S · Answer

Hy ​@waystone1736Most Likely CauseStale field mapping– The filter step still references a field from an older version of the trigger. If you changed the trigger app, event, or if WellnessLiving updated its field structure, the mapped field path no longer exists. The filter receives(missing value)because it's looking for something that isn't there.You can try:Delete the existing rulein the Filter stepRe-add the rule– Select the field fresh from the trigger's output dropdown (don't type or reuse old mapping)Republishthe ZapHope this helps you get it sorted!If you're still stuck, I offer a free 20-min Zapier troubleshooting call. Book it through my Zapier Directory profile — it's listed under Resources on the left side: https://zapier.com/partnerdirectory/automatemybiz!-->