hi @kpang!
Thanks for your message!
A few initial questions:
- Is the user with the issues getting it when first annotating or are they able to annotate/save but then some time later get the error?
- Have you modified your
feed_overlapsetting? It defines whether to send out each example once so it’s annotated by someone (false) or whether to send out each example to every session (true). By default it isfalse. - Do you know what browsers (Chrome, FireFox, etc.) your annotators are using? anything unique in the user reporting issues versus you/users who are not?
- Just to confirm, when you say you've enabled "multi-session", you mean you've added
?session=xxxto each annotation app URL's, correct? Are you saving them all to the same Prodigy dataset?
The message in the app is usually shown when Prodigy itself raises an error and stops the server. The problem is it can be due to many different causes.
Can you you tell if there's an error message in your terminal? That should explain what the underlying problem was that means that the app couldn't start – like a data validation issue, or something else. One alternative is to enable logging by prefixing your command with PRODIGY_LOGGING=basic or PRODIGY_LOGGING=verbose (more details).
If you don't see an error in your terminal, then it may not be a server-side problem but a client (browser). This would likely be the case if others don't see the same bug. Can you ask the annotator to try to open their browser's developer console (e.g., Chrome) and see if there's an error there. That may help too.
I've found another instance of EC2 + multi-session where the user received the error. It may not be relevant and for a different underlying cause, but providing just in case.
Hope this gives you some help and hopefully we can figure out this issue.