If the participants go to Qualtrics first then I am more surprised by the Pavlovia Shelf issue, since they should be spread out by the time they get to Pavlovia.
You can make an entry mandatory by adding a * or |req at the end of the field name, e.g. Prolific ID*
While bugs can be formally reported as issues on GitHub
and
I am not sure if that makes them any more visible than posting here.
Perhaps the best option would be to open a Github issue and link to it from here. I am certainly more likely to see it here than on Github, but the opposite might be true for some of the developers.
We use a system called ClickUp to keep a track of bugs and features. I have added a link to this thread to the ClickUp called “Clash between periodic saving and psychoJS.quit” which I created in July 2024 based on this thread Error message when quitting the experiment under certain conditions . Testing with large numbers of simultaneous participants is particularly difficult.
PsychoPy is maintained by a small team, which is why we are able to keep our prices lower than for similar products (free in the case of local experiments). Unfortunately, this currently means that we only have one person able to work on Pavlovia functionality (including Pavlovia Surveys) which is why bug fixes and developments progress more slowly than we would like.
What version of PsychoPy are you using?
Has periodic saving allowed you to recover any data? As far as I can tell it is causing the data loss, and I do not use it in any of my own experiments.