I'm trying to startup (Open) a newly deployed oTree application on Heroku.

I am seeing the following in the application log:

******************************************************************************************8
Application Logs
2023-02-25T11:54:32.195746+00:00 heroku[web.1]: State changed from starting to crashed
2023-02-25T17:33:10.161239+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=schampsystems.herokuapp.com request_id=2f191641-8969-461b-83f9-3d12a4e27cf5 fwd="199.15.222.106" dyno= connect= service= status=503 bytes= protocol=https
2023-02-25T17:33:10.377366+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=schampsystems.herokuapp.com request_id=f6e13afc-c970-4b69-bd3e-2ae436067eb7 fwd="199.15.222.106" dyno= connect= service= status=503 bytes= protocol=https
2023-02-25T17:45:15.256691+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=schampsystems.herokuapp.com request_id=ed601513-5b28-4e3a-9856-29b3d8107e05 fwd="199.15.222.106" dyno= connect= service= status=503 bytes= protocol=https
2023-02-25T17:45:15.614259+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=schampsystems.herokuapp.com request_id=32cba94d-fd47-4e90-b02a-336dee9f5d36 fwd="199.15.222.106" dyno= connect= service= status=503 bytes= protocol=https
2023-02-25T17:46:09.058496+00:00 heroku[web.1]: State changed from crashed to starting
2023-02-25T17:46:51.355663+00:00 heroku[web.1]: Starting process with command `otree prodserver1of2`
2023-02-25T17:46:52.799086+00:00 app[web.1]: bash: line 1: otree: command not found
2023-02-25T17:46:53.022349+00:00 heroku[web.1]: Process exited with status 127
2023-02-25T17:46:53.108724+00:00 heroku[web.1]: State changed from starting to crashed

******************************************************************************************************

Did I miss a configuration step?

Are you deploying through oTree Hub?
This issue should not occur unless you are managing your requirements.txt manually and forgot to include otree in it.

Are you deploying through oTree Hub?
This issue should not occur unless you are managing your requirements.txt manually and forgot to include otree in it.

Thanks Chris,

I changed the requirements.txt so oTree could overwrite and that fixed the issue.