I have a participant list of about 15,000 emails. I've generated tokens, and I've confirmed running count(distinct)) on the tokens table that all tokens are indeed distinct.

I started sending email invitations, using this html in the email:

After sending out several 1000 emails, we have had some participants report back that when then click on the link, they get the notice:

This invitation has already been used.
We are sorry but you are not allowed to enter this survey.

When I check the token in their invitation email, I see that the token is for another participant (a test record we created -- the 2nd row in our token table).

Any ideas why some participants would be receiving the wrong token ID in their invitations?

I'm running version 2.67.1, build 170626.

This has occurred again, on a second, different survey.

After using the Send Invitations screen to send to ~3000 participants, we received reports of people receiving invitations with same token.

To test, we added a test participant to the survey with a token of ABCD1234 and sent an single invitation. In the invitation, we used the URL like:

and beneath it, we used {SURVEYURL}

The {token} URL had wrong tokenID -- but the {SURVEYURL} had the right token ID. See attached image.

I found bugs.limesurvey.org/view.php?id=9862 was reported in 2015, and sounds similar to issue we are experiencing... but that was fixed long ago... or was it?

If you can reproduce with a simple string, for example
- SURVEYURL : {SURVEYURL}<br>
- TOKEN : {TOKEN}<br>
- TOKEN:TOKEN : {TOKEN:TOKEN}<br>

It's great to report the bug (and maybe TOKEN:TOKEN is OK here ?)

PS : else : why you don't use @@SURVEYURL@@ ?
www.limesurvey.org/manual/Survey_partici...s#Email_placeholders

Thanks, I'll run some tests and see if I can get useful information to add to a ticket.
I do know that this issue occurred between early June and now -- as I have another survey where we used {TOKEN} in the HTML for the link, and everything sent okay.

I have had the same problem recently. I am using domain alias.

Good to hear another person had this issue (although sorry you had to!). I planned to test various scenarios to recreate this scenario so I can report a bug, but I'm currently on vacation, so will have to wait until August 1st.

I've had a second survey where this occurred, this time when {token} was used in the body of the email reminder, not when embedded as part of the survey Url.

In both cases, the surveys were multilingual, if that has any bearing on things.

I have the same problem about using {TOKEN} in my email template, please fix that!

artemis wrote: I have the same problem about using {TOKEN} in my email template, please fix that!

You might raise the attention of a developer with submitting a bug ticket.

DenisChenu wrote: If you can reproduce with a simple string, for example
- SURVEYURL : {SURVEYURL}<br>
- TOKEN : {TOKEN}<br>
- TOKEN:TOKEN : {TOKEN:TOKEN}<br>

It's great to report the bug (and maybe TOKEN:TOKEN is OK here ?)

But for sure : using TOKEN:TOKEN work better

So, is the recommendation to use(?):

<a href=" mysurveyurl.example.com/index.php/762788...TOKEN:TOKEN}&lang=en ">Click here to begin survey