Skip to main content
Question

Is my branching breaking my tagging logic?

  • June 28, 2026
  • 6 replies
  • 76 views

I have a form that screens out candidates. If they answer a question in a way we don’t like, they are immediately routed to the “thank you, but no” ending screens. This happens on questions 1, 2, and 3. If they get through all three screening questions, then they continue onto questions 4 through 6 as normally.

So I have branching

  • On question 1, for answers c and d go to ending A, all others continue
  • On question 2, for answer d go to ending A, all others continue
  • On question 3, for answer d go to ending B, all others continue

So a 1d candidate will show up in results as null for the rest of the form, a 1a, 2d candidate will have two answers with null for the rest, and a 1a, 2a, 3d candidate will have three answers filled in with the rest of the the form blank. This all seems to trigger fine.

 

I’m also trying to tag them at the same time. 

  • Tag as Low when 1 is c or 1 is d or 2 is d or 3 is d
  • Tag as high when 5 is a and 6 is a
  • All other cases tag as Medium

I’m testing my first case (1d) and it’s showing up as tagged Medium.

 

There’s one more branch at the end:

  • On question 6, if tag is high, go to ending C, all others ending D

There isn’t any other logic involved.

What am I doing wrong? Are the null items messing with it?

6 replies

  • Author
  • Explorer
  • June 28, 2026

After further testing, this seems to be because not all three questions are answered. It triggers correctly for 1a, 2a, 3d but not for 1d and not for 1a, 2d. 


john.desborough
Forum|alt.badge.img+6
  • Certified Partner & Champion
  • June 28, 2026

@TwoThirty - can you show screen shots of your logic rules please and or a loom/video showing them? 

that will help troubleshoot

 

des


  • Author
  • Explorer
  • June 29, 2026

 

Tagging is 

 


  • Author
  • Explorer
  • June 29, 2026

@TwoThirty - can you show screen shots of your logic rules please and or a loom/video showing them? 

that will help troubleshoot

 

des

Sorry. I think I put that as a general reply to myself. Is the above ok?


john.desborough
Forum|alt.badge.img+6
  • Certified Partner & Champion
  • June 29, 2026

@TwoThirty - what i would do to troubleshoot this is to remove the OR condition and test each statement as a stand alone. both for the logic and for then for the tagging. 

like this: with this condition below, have it go to ending B

 

then do the individual condition for what was on the OR side of the earlier rule.

do that for all the logic and test it out - i have, over time, seen some funky things happen with the logic rules and the boolean connectors. 

try that out first on the logic. one rule per choice. and then if that doesn’t correct it, we’ll look at what else might be going on


  • Author
  • Explorer
  • June 29, 2026

@TwoThirty - what i would do to troubleshoot this is to remove the OR condition and test each statement as a stand alone. both for the logic and for then for the tagging. 

like this: with this condition below, have it go to ending B

 

then do the individual condition for what was on the OR side of the earlier rule.

do that for all the logic and test it out - i have, over time, seen some funky things happen with the logic rules and the boolean connectors. 

try that out first on the logic. one rule per choice. and then if that doesn’t correct it, we’ll look at what else might be going on

The branching routes correctly. It’s the tag that is the problem. If I delay branching until the third screening question, then the tagging works properly. I think it doesn’t know how to evaluate the tag if one of the answers is NULL.