Please help us help you and fill where relevant:
Your LimeSurvey version: LimeSurvey Cloud Version 5.3.8
Own server or LimeSurvey hosting: LimeSurvey hosting
Survey theme/template: Fruity
==================
Hi!

I have read multiple threads on the difference between token based response persistence and resume later and I understand that is is unnecessary to have both the resume later function AND the token based responses persistence ON in an non-anonymized token based survey. BUT is it "harmful" to have the resume later function on whilst having the token based persistence on as well in this type of survey?

Thank you.

I always thought there is no use for "resume later" together with "token based response persistence", but it seems like there is one small advantage to allow it: With "token based response persistence" only the data before the current page is saved. If the respondent answered questions on the current page, this data is gone if they just close the window and come back via the link. So they either have to answer the whole page and go on "next" and leave then or they would need to use "resume later".

Personally, I don't like the "resume later" function in general, but I don't think that it can harm. Let's see what others have to say about this topic.

It does no harm to have both enabled.

And if so, as Holch points out, the "Resume later" button simply allows you to save answers without advancing in the survey.

I have used to "Save and resume later" a very few times. This resulted in lost passwords and extra help via email. In the end this resulted in no extra responses and a lot of work. I decided to never use it again.

This resulted in lost passwords and extra help via email. In the end this resulted in no extra responses and a lot of work.

This is also my main fear with this feature. I always like to keep it simple. If it is a long open survey it is probably the only viable option we can offer, but with token based surveys I think I prefer the fact that they loose the data on the last page (usually not a big deal anyway, because I try to have only 1 question per page, certainly for longer questions).

The thread started with the premise that both the resume later function and token-based response persistence are enabled.

In this case there is little or no risk as the password dialog is never loaded when clicking resume later. The answers are recorded and the page simply reloads.

Use case:

I have developed several surveys where there is a requirement that several people are allowed to respond to the same data set (token) before final submission. For example a single token for a country with several "experts", all contributing.

In these surveys, there are often many quite complex questions in a single page that may not all be answered by the same person, so it is a nice feature to allow an "expert" to answer some parts and save them without moving forward in the survey. This allows the next "expert" to access the survey via token-based response persistence and continue. Particularly in the last group where moving forward would submit the survey and prevent any more access.

In these cases, in the theme TWIG files, I modify the "Resume later" button to say "Save answers".

tpartner wrote:

The thread started with the premise that both the resume later function and token-based response persistence are enabled.
In this case there is little or no risk as the password dialog is never loaded when clicking resume later. The answers are recorded and the page simply reloads.
 

That is not common knowledge Cause we are all afraid to use the function, I guess. This is the first time I read about the different behaviour in combination with token-based respone persistence.
I cannot remember reading about that in the manual as well.
 

Thank you Tpartner for sharing your experience. I did not expect the behaviour of "resume later" to change in combination with token-based response persistence. Good to know!