4👍
✅
What you are trying to do (i.e. embed beat inside the worker) isn’t recommended anyway. So I’d suggest you start a standalone Celery beat (as adviced by the error message) and worker(s) with gevent pool. The worker’s part is where you take advantage of gevent as they execute the I/O bound tasks, not the Celery beat that just kicks them off.
Alternatively, if you use Celery 4.4 or newer, you might try to use --pool threads
to you threaded task pool.
Source:stackexchange.com