Error when loading running experiment (referencing preload queue)

URL of experiment:
https://run.pavlovia.org/lsknaup/sfb940a1-b02

Description of the problem:
I received complaints from participants about problems starting the experiment and entering their participation code. I checked that the codes are correct and asked participants to reload the URL in a private window in case they entered a wrong code before. This has helped with other problems but has not solved the current error. Now, when i tested it again on my own computer, i received error messages stating problems with the preload queue at random and different files (see screenshot).

About the participation codes: In my experiment, each participant receives an individual code and this code is matched with a specific triallist via a file listing and matching each code to one triallist file (file_list.csv). So at the beginning of the experiment there is a text field where participants enter their codes and they can only progress with the experiment, if the code is correct (i.e. text matches one of the codes in the file list).

I am using version 2024.1.4 and it worked fine previously (i primarily use Firefox as a Browser).

If these were errors around 11am today then they may have been caused by the server struggling with unusually high load. Please try it again now.

Yes, this appears to be the root of the issue, as the error has not reoccurred so far. Thank you for your quick response, I really appreciate the help!

Just a quick follow-up question: I have received several emails regarding issues with data saving and the redirection link at the end of my experiment. It also seems there may have been some data loss starting from Tuesday evening. Could the problems related to unusually high server loads have begun earlier than yesterday around 11 AM?

Perhaps it’s just a coincidence, but I was wondering about this because issues like data loss and faulty redirection links, in my experience, occured only very rarely.

I can see evidence of a 7 minute outage around 6am on Tuesday morning, but nothing between that and the incident around 11am Wednesday. However, I agree that other sporadic failures over the past couple of days may well have had the same cause.

1 Like