Comment on page
Additional variant settings
When this flag is enabled, every time a responder returns to a flow they are treated as a new responder. This will occur whether or not they have completed the flow. No answers are loaded, and progress will not be maintained. Additionally, a new responder UUID is generated at each visit.
You can still force-load a particular responder UUID by passing the UUID in as a URL parameter. See Setting the responder UUID manually for more information.
When this setting is disabled, returning responders will retain their responder UUID. This is the default behavior. A user is considered a "returning responder" when they revisit a flow using the same browser they initially started their flow from.
Allows the ability to use the browser's forward and back buttons to navigate through a flow. This is not currently supported in embedded flows.
When Enable restart once flow completed is toggled on, users will be given the option to restart a flow if they return to it after completing. Users will keep the responder_uuid generated during their initial visit, but Formsort will discard saved answers to allow them to start the flow over.
Answers are only cleared at the user end. Any answer payloads sent to your data stores will persist in your data store.
This is useful for forms that need to be filled out multiple times by the same users, but also forces users to fully complete a form before starting a new one.
If your flow is embedded into another page, this will create a link to close the embed once the flow is completed.
If autosave is enabled, it will cause the form to retain a responder’s answers should they leave and come back to the flow. In-progress answers are saved after 3 seconds have passed from a responder’s input. Answers will also be submitted to enabled integrations if "When the flow is finalized or abandoned" is enabled in submission frequencies.
Last modified 1mo ago