Test a returning visitor or restart a survey
If your survey skips questions or won't restart, you'll find how to check saved answers, widget settings, and dismissal without changing things for real visitors.
You can restart a survey for testing or change whether returning visitors see the same questions again. Choose the fix that matches what you want. Reloading the page doesn't make you a new visitor, so saved answers and widget settings still apply.
My survey skips questions I've already answered
If you want real visitors to repeat the quiz, change the widget's question handling:
- Open Widgets and select the widget.
- Open Display.
- Expand Question handling.
- Choose Ask every question, every time.
- Repeat for every widget that displays the survey.
- Review and publish the change.
When the widget uses Ask questions we don't know the answer to, it skips questions this browser has already answered. Keep that setting if returning visitors should answer only missing questions.
Changing this setting affects real visitors. To restart only your own test, use the debugger controls below.
The widget doesn't appear at all
Check After it's dismissed, targeting, devices, and triggers. Then inspect the flow's final path. See widget display troubleshooting for those checks.
The widget may still be dismissed, excluded by targeting, waiting for a trigger, or following a path with nothing to display. Changing question handling doesn't clear dismissal or make an excluded visitor eligible.
I want to start over without changing the live survey
Use a fresh private browsing session to test as an unknown visitor, or use the reset controls in the authorized debugger. Your normal browser keeps its answers and other visitor data between visits.
- Note whether you're testing the draft or published configuration.
- Start with fresh visitor data.
- Run the survey and note your answers.
- Return in the same browser session to check what it remembers.
- Test dismissal separately.
A preview reset and an ordinary returning visit are different tests. Check both if you're changing what returning visitors see.
Which debugger reset should I use?
| If you'd like to... | Use this control | What it clears |
|---|---|---|
| Start the flow over in this debugging session | Flows → Restart flows for this session | The debug session's answer bank, inputs, scores, stored variables, flow progress, dismissal state, and split-test overrides. Then it restarts the flows. |
| Show a widget you've dismissed during testing | Flows → Clear dismissed | The dismissal state that prevents the widget from running. This control appears when dismissal blocks a widget. |
| Remove this browser's real visitor data | Visitor → Clear this browser's RightMessage data | The real visitor's data in this browser, after confirmation. This goes beyond the debugging session. |
Note your test overrides before restarting flows. Restarting clears more than the current step, but it doesn't delete every answer saved in the real browser. Use a fresh private session if you want an isolated unknown visitor without deleting your normal browser's data.
If you've forced an A/B test variant in the debugger, return the selector to Automatic assignment to check normal assignment. A forced variant can explain why you keep seeing the same content.
A Router skips a question I expected to see
Inspect the path the visitor took before changing question handling. Use a Question node when visitors should answer. Use a Router when an answer you already know should choose the branch.
A Router reads a known answer without asking the question. A Condition can also deliberately send visitors past questions.
Test with a fresh visitor, a partially answered survey, and a fully answered survey. See returning visitors and missing answers for how to set up those paths.
The survey skips every question
In Question handling, choose Ask questions we don't know the answer to to collect missing answers over time. Choose Ask every question, every time for a repeatable quiz.
If the setting is Skip the questions, the widget moves toward the first offer or form on the selected path.
Changing question handling doesn't rewrite the flow's branches. A Router can still bypass a question, and the flow can still end before reaching later questions.
It works for some returning visitors but not others
Compare these cases on the same page and configuration version:
| Visitor's saved data | What to check |
|---|---|
| No previous answers | The first reachable question appears. |
| Only the first answer is known | Unknown-only handling skips that question and asks the next missing one. |
| All answers are known | Unknown-only handling reaches the end of the path instead of repeating questions. |
| The widget was dismissed | The widget can stay hidden even when answers are missing. |
Note which case fails before changing the flow. When each visitor sees the questions they should, test one final return visit outside the debugger.