Hello - wondering if anyone can explain this error?
A client received it twice after clicking on a public survey link from survey123. On the third try, he was able to get through to the survey but I am hoping to avoid this error in the future if possible.
Hi Dena,
Are you still seeing this issue? If this occurred at ~9:30 or so yesterday, that was due to preparations for the 3.7 release of Survey123.