Currently, timeout dates are either relative (2 days) or absolute (2020-05-11), but are set directly in the Typeform question description and, like the rest of the survey, are immutable once created.
In reality, however, many survey creators want to change the timeout after they set it. For example, they might think they will be ready to send a second wave of surveys on the 10th of October, but in reality need an extra month. Or, they might have accidentally set it to the 10th of November and want to move it up. Both of these things have happened to us!
Possible solutions:
Make a "timeout" a mutable concept for a survey, managed in the dashboard somehow, and the survey itself refers simply to a timeout ID of some sort (that must exist on importing the survey to avoid a bad state?). This would definitely require some dashboard thinking to visualize timeout times for surveys.
Use some new version of "bailouts" in some fashion to allow users to "swap out" a respondents survey at any time, which could solve all sorts of problems including the timeouts. This is a more "implementation first" solution, but may be quite simple and powerful actually.
Currently, timeout dates are either relative (2 days) or absolute (2020-05-11), but are set directly in the Typeform question description and, like the rest of the survey, are immutable once created.
In reality, however, many survey creators want to change the timeout after they set it. For example, they might think they will be ready to send a second wave of surveys on the 10th of October, but in reality need an extra month. Or, they might have accidentally set it to the 10th of November and want to move it up. Both of these things have happened to us!
Possible solutions: