## We get it, Logic Jumps can be tricky sometimes. This is why we’ve put together this checklist of common Logic Jump issues for you. You can always turn to this list before blaming the universe for lacking logic and thinking that everything is descending into chaos (:

### 6 things that could be messing up your Logic Jumps

### 1. Your Test Logic is off

When you’re working in the Live Preview of the Typeform builder, make sure you turn on the **Test Logic** option in the top right corner. This should always be the first step when troubleshooting Logic Jump issues. If the icon is green, like in the screenshot below, you’re good to go:

### 2. Your Logic Jumps are in the wrong order

Make sure you’re adding Logic Jumps in the correct order. Head to this article to learn what’s important when it comes to ordering Logic Jumps.

The first rule of thumb you should try to keep in mind about the logic of Logic Jumps, is that Logic Jumps can’t go back to a place that they haven’t been to before. When adding multiple Logic Jumps to your typeform, make sure that you’re not adding conditions based on previous questions.

For example, if you set a Logic Jump from your first question to your fourth question, then you’re skipping the second and third questions. These questions will not be included in the logic path of the typeform, and the form will just end after jumping to the fourth question without going back to the second and third questions.

### 3. You’re not using AND/OR operators correctly

Make sure that you’re using the AND/OR operators correctly. Head to this article to learn more about how to use them when setting conditions for Logic Jumps.

- Never use both AND/OR conditions in a single Logic Jump. The solution in the screenshot below follows the logic of operators, but it won’t work with Logic Jumps:
- Always add a separate Logic Jump when you start using a different operator type. Just remember to use AND with AND and OR with OR. This will keep your Logic Jump structure nice and tidy, and you’ll be able to eliminate conflicting AND/OR operators.

### 4. Something’s wrong with your personality quiz

Check for specific issues when creating personality quizzes. You can also read this article and check out this template to learn how to become a master personality quiz builder using Logic Jumps.

- Make sure you add scores in the correct order for each of your questions. Scores will be added up in the end, and a personality type will be determined based on that score. These calculations can only be correct if the same score is consistently added to the same option in each question.
- If your user can earn 1 point for answer A, 10 points for answer B, 100 points for answer C, and 1000 points for answer D, then you must always add the same score to the corresponding answer.

Consistent scores will guarantee that you can match personality types to scores correctly, just like in the example below:

- Use the OR operator instead of AND when adding Logic Jumps to scores. Using the AND operator would mean that your Logic Jump would have to meet all of the conditions listed simultaneously for it to work. You can also check out this article to learn how to add Logic Jumps to scores.

In the example below, the scores from the answers are connected by an AND operator, which means that they would only jump to the selected question if someone reached all the different scores at the same time. This scenario would require more magic than logic (:

Instead of the solution above, simply use the OR operator to show different Thank You Screens or questions based on different scores in a quiz. Here’s an example that would work perfectly with different scores:

- You can also check if
**Randomized**is enabled in your Multiple Choice or Picture Choice questions. Disabling it might help with Logic Jump issues, depending on the use case, but this is not a general solution. You can read more about randomizing your questions here.

### 5. You forgot to set “reminder” Logic Jumps

When multiple selection is enabled, and you’re using multi-branching, don’t forget to set up what we sometimes call “reminder” Logic Jumps. The logic behind this is that if you only add Logic Jumps to the first question, your follow-up questions won’t “remember” these Logic Jumps when multiple options are selected.

What? Logic Jumps have the memory of goldfish? Read on to learn how to teach them to remember. You can also read this article to learn more about the difference between single-branching and multi-branching.

In the scenario below, **Multiple selection** is enabled, and I want to add Logic Jumps to follow-up questions as well to cover all possible multiple selections.

This way I’m basically setting the same Logic Jumps for the follow-up questions as for the first question while eliminating questions that I’ve asked before.

- First add Logic Jumps to all the options in the first Multiple Choice question.
- Then add Logic Jumps to all the follow-up questions the Logic Jumps go to from the Multiple Choice question. When adding “reminder” Logic Jumps to the follow-up questions, the first follow-up question will have to jump to all the remaining (in this case three) follow-up questions. The second follow-up question will have two Logic Jumps for the remaining options, and so on. There is no need to add a “reminder” Logic Jump to the last follow-up question.

This is what the overview of the questions with Logic Jumps and the “reminder” Logic Jumps added to the follow-up questions will look like:

### 6. You’re not using “reverse logic” with blank fields

When adding Logic Jumps to blank fields, make sure you’re using “reverse logic”. You can add Logic Jumps with negative conditions to blank fields, but you cannot use positive conditions, like **is equal to**.

In the scenario below, I want to jump to Thank You Screen A. when someone leaves the answer field empty, and I want to set up my conditions accordingly.

In the screenshot below, a Logic Jump with the is equal to condition and a blank field is used. This might seem like a logical approach, but Logic Jumps don’t work this way.

What you can do instead is use negative conditions and “reverse logic”. Add the **is not equal to** condition to the blank field, and the question you want users to jump to when they don’t leave the answer field empty. Below is an example of the method that will work seamlessly with Logic Jumps:

Didn’t find the answer to your Logic Jump problem? Contact us using the button below and we’ll be happy to help. Your feedback and questions help us improve Typeform:)