Why My Path Isn't Being Triggered

Forgot to mention that if you need me to provide anything else, feel free to ask!

Hi ​@BR2227 

You should use these conditions for each Path Filter:

• [VAR] greater than #
• [VAR] less than #

For live Zap Runs, check your history details to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/

If you still need help, post screenshots from your live Zap Runs history DATA IN/OUT.

Is this what you need ​@Troy Tessalone ? Sorry I am pretty new to all of this! Thanks for your help!

​@BR2227 

We need to see screenshots of the DATA IN/OUT for the Path Filter steps in the live Zap Run, not from the Zap Editor while in EDIT mode.

In your recent screenshots, you only did that for Zap step 1.

​@Troy Tessalone 
Is this right? There is no Data In Or Out becuase it didn’t run the path?

​@BR2227 

Here’s the issue…see screenshot below.

Notice the mapped variable value shows: “ 6\n\n”

That means there is a leading space and 2 trailing line breaks.

That is why the Filter condition did not evaluate as expected, because the variable value is not a number.

To fix, add this Zap step after the Formatter Step 6 and before the Paths: Formatter > Text > Trim Whitespace

That will remove leading/trailing whitespace, which should leave you with only a number.

IMPORTANT: Then update the Path Filter conditions to map/use the output variable from the new Formatter step.

Thanks ​@Troy Tessalone ! That 6/n/n is gone and I updated the path conditions to use the output of the whitespace formatter I just added… It is still saying path conditions aren’t met.

Thank you so much! It’s working now!

Wow! Thank you for confirming that Troy’s resolution got the Zap running. This will significantly help our Community members to have as a reference for the same issue.