Since steps are easily re-arranged within the flow, it is useful to assign a step ID to a step to maintain stable references to steps, as their index within the flow or text labels may change. This is particularly useful in the context of analytics, where understanding how the same step performs across versions is important.
Step IDs are not required - if they are not set, the step index will be sent along with any analytics event payloads. When set, they are required to be unique.
If defined, Formsort will attempt to advance to the next step after the specified timeout. This allows making interstitial screens that show information to a responder without requiring them to provide any answers.
This will only succeed if the responder has provided valid answers to all of the questions on the current step, the questions are all optional, or the content on the step does not require answers, such as informational content.
If your answer submission frequency is set to On savepoint, checking Is savepoint will ensure that the responder's answers are submitted to your destinations at the completion of this step.