Automation Answers

Why Is My Zapier Path Running the Wrong Branch?

A Zapier Paths step runs the wrong branch when rules overlap, compare numbers or dates as text, or hit a blank or oddly formatted value.

By Automation Ace Editorial Team · Reviewed for technical accuracy by Troy Tessalone · Published · Updated

Short answer

Why Is My Zapier Path Running the Wrong Branch?

In Paths by Zapier, each path checks its own rules, and every path whose rules are true runs. Paths aren't an either/or choice. A Zap takes the wrong branch, more than one branch, or no branch at all when rules overlap, compare the wrong type of value, or meet a blank or differently formatted field. Check each path's rules against the live value, make the rules exclusive, and add a catch-all path for anything that matches none.

Common causes

  • Two paths have rules that can both be true, so both run.
  • A number or date is compared as text, so 100 is treated as smaller than 9, or 1,200 isn't read as a number.
  • The field has extra spaces, different capitalization, or a slightly different label than the rule expects.
  • The field is blank in some runs, so no path's rules are true and the Zap stops.
  • The rule maps a field from the wrong step, or from a sample that differs from live data.

Diagnostic steps

  1. Open the run in Zap history and note the exact value each path checked and whether it ran.
  2. Use number or date conditions for numbers and dates, and remove commas or currency symbols with Formatter first.
  3. Rewrite the rules so they can't overlap, for example less than 1000 and greater than or equal to 1000.
  4. Add a final path for values that match nothing, and send it to a person or a log.
  5. Retest with a value just below, at, and just above each threshold.

Example

Path A runs for deals over $5,000 and Path B for deals under $10,000. A $7,500 deal runs both paths and creates two tasks. Changing Path B to under $5,000 makes the paths exclusive.

Caveats

Paths are good for a few clear branches. When the logic depends on many values, a lookup table or a Code step is easier to maintain. A filter or path that stops a run early can also hide problems, so log the runs that match no branch.