#1 by ErikdeKwaadsteniet

We are now running a study on heroku using otree 3. It all works fine, except that players get stuck on waitpages until they refresh. Locally, it works fine. What could be the cause of this, and how to solve it?

#2 by Trontatuma (edited )

I have the same error!!! One patch is put an auto-refresh on the wait page. But I am not sure if this is stable as it does not really solve the error.

#3 by ErikdeKwaadsteniet

Thanks for the tip! Do you also use an old version of otree/python on heroku?

#4 by Trontatuma (edited )

No, I am on Otree 5 with Heroku

#5 by simoncolumbus

Hi Erik, Trontatuma -- did you find a solution for this? I am encountering the same issue in oTree 5 -- if you found a way to solve this, I'd be eager to learn how!

#6 by ErikdeKwaadsteniet

Hi Simon,

I don't think we solved it. I think the otree version we used was just too old to run on heroku then, so I guess it must be another issue.

I hope you'll solve it soon!

Erik