Describe the bug
We do celery worker -B in Heroku's Procfile.
But Celery docs say "You can also embed beat inside the worker by enabling the workers -B option, this is convenient if you’ll never run more than one worker node, but it’s not commonly used and for that reason isn’t recommended for production use". See: https://stackoverflow.com/questions/51393150/why-does-celery-discourage-worker-beat-together
Additional context
Consider removing -B option from celery worker in Procfile.
Describe the bug We do
celery worker -Bin Heroku'sProcfile. But Celery docs say "You can also embed beat inside the worker by enabling the workers -B option, this is convenient if you’ll never run more than one worker node, but it’s not commonly used and for that reason isn’t recommended for production use". See: https://stackoverflow.com/questions/51393150/why-does-celery-discourage-worker-beat-togetherAdditional context Consider removing
-Boption fromcelery workerinProcfile.