Willkommen im Online-Support von SoSci Survey.

Hier bekommen Sie schnelle und fundierte Antworten von anderen Projektleitern und direkt von SoSci Survey.

→ Eine Frage stellen


Welcome to the SoSci Survey online support.

Simply ask a question to quickly get answers from other professionals, and directly from SoSci Survey.

→ Ask a Question

0 votes

Greetings,

I am now finishing development on a multi-wave daily study. I love this platform and your support has been fantastic. I seem to have one more problem which I can easily work around but I wanted to alert you to it and make sure I am not doing something wrong.

I am using mail resume to send a note 18 hours after a participant reaches an interrupt page. I put in this code: mailResume(false, 1, 64800). I also have a second mail resume for 24 hours which looks like this: mailResume(false,13,86400), 1 and 13 are of course the mailing reference numbers.

In my final testing I am finding that the mail that should come 18 hours later is coming 12 hours later and the mail that should come 24 hours later is coming 18 hours later. My guess is that this is timezone related as I believe I am exactly 6 hours behind Germany. I can easily adjust by just putting in different numbers but before doing that I want to make sure there isn't some other remedy. I should also note that I did set the time zone in the Experimental setting tab in project settings to America/New_York. If it would make more sense to change that I could do that also.

in SoSci Survey (English) by s108637 (150 points)

1 Answer

0 votes

I should also note that I did set the time zone in the Experimental setting tab in project settings to America/New_York.

Thanks for the feedback. Yes, you are probably true that this causes the problem.

Wile the UNIX timestamp is UTC, mailings are currently stored with a GMT+1 send time. However, internal calculations use the time zone you have set in the project.

Actually, I was hoping that you won't need mailings, because we already knew that there might be issues. I think the best solution was to resolve this issue very soon. However, if you used 6 more hours as a workaround, this won't work any more after we repaired the feature.

by SoSci Survey (68.1k points)
...