Celery Beat sends to workers tasks that do not exist
I saw a lot of similar questions but nothing helped.
Every now and then I am receiving the following error: ‘app.tasks.do_some_work’. When I check inside the Django container, Celery Beat container, or Celery Worker container’s app.tasks module, I don’t see any task with that name.
Celery Beat sends to workers tasks that do not exist
I saw a lot of similar questions but nothing helped.
Every now and then I am receiving the following error: ‘app.tasks.do_some_work’. When I check inside the Django container, Celery Beat container, or Celery Worker container’s app.tasks module, I don’t see any task with that name.
Can Celery Be Used for Background Tasks Without Redis in Production?
I have an API that needs to upload large files to S3, with file sizes close to 10GB. I want to handle this as a background task and am considering using Celery. However, the client won’t accept the additional cost of using a Redis service.
How to profile Celery / Django in docker?
I have a Django / Celery application