> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/form-behavior-settings/variant-settings/returning-responder-behavior.md).

# Form behavior for returning users

What happens when visitors return to a flow they already started on?

When a user returns to a form they previously started but didn’t finish, you can control where they re-enter the flow. This behavior applies to both **standalone flows** and those **embedded into your sites**.

By default, Formsort stores a responder’s answers for about **3 weeks**. After that, stored data associated with their `responder_uuid` is purged, and they will start fresh on their next visit - **unless** you've changed configuration of the settings below. 

Go to the **Settings** tab in any variant and look for **Returning responder behavior** to find the configuration menu.

{% hint style="info" %}
For more information about answers storage, see our [data retention policy](https://docs.formsort.com/handling-data/philosophy).
{% endhint %}

<div align="left"><figure><img src="https://1036686854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJPnL__mOdr_mLZ8nwf%2Fuploads%2FEm772FeEnAtA9cYY1K7L%2Fimage.png?alt=media&amp;token=a6ed5d0a-c94b-438f-b892-de9856fff2b3" alt="" width="353"><figcaption></figcaption></figure></div>

***

### Options

#### Start each session as a new responder

When enabled, every visit is treated as a brand new session:

* **No previous answers** are restored.
* A new `responder_uuid` is generated on **every visit**, including page refreshes.
* The user is not **pinned to a variant** they previously saw.
* Any Formsort-related **cookies are cleared**, including [external variable](/response-data-collection-and-management/variable-schema/external-answers.md) cookies.

This setting is useful if you want users to **always start fresh**. For example, they can restart the form by simply refreshing the browser or opening it in a new tab.

If you [force-set a responder UUID](/core-concepts/how-data-works-in-formsort/responder-uuids.md#manually-setting-the-responder-uuid) manually via URL, answers from previous sessions won’t be restored.&#x20;

{% hint style="warning" %}
If this setting is **disabled**, Formsort stores the responder’s UUID in browser cookies. When they return to the form using the same browser, their **previous answers are restored**.
{% endhint %}

Learn more about [responder UUIDs](/core-concepts/how-data-works-in-formsort/responder-uuids.md) and how Formsort tracks responders.

### Resume session on page refresh

This setting is only available when "Start each session as a new responder" is enabled. It allows users to resume their session after a browser refresh, preserving their `responder_uuid` and the state of the form up to that point.

### Start at furthest point

(Default behavior)\
Responders will resume the form from the **furthest step** they previously reached. All previous answers will be restored.

This allows users to **continue where they left off**, even after refreshing their browser.

### Start at beginning, discard answers

Responders will restart the flow at the **beginning**, and previous answers will be **discarded**. However, their existing `responder_uuid` will still be used.

This is useful when users should **start over**, but you want to **retain their responder identity** for tracking or analytics purposes.

### Start at beginning, keep answers

Responders start at the **beginning** of the form, but their **previous answers are restored** into the fields.

This is helpful when you want users to **review or revise** their answers during a second pass through the form.

{% hint style="info" %}
Want to learn more about other behavior settings? Go back to the [Settings](/form-behavior-settings/variant-settings.md) overview section.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.formsort.com/form-behavior-settings/variant-settings/returning-responder-behavior.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.