django-celery-beat VS django-celery-results

I was looking for a nice way to manipulate periodic tasks in Celery. I found an amazing django-celery-beat package that provides PeriodicTask database objects. With PeriodicTask objects, you can dynamically add/remove/update periodic tasks in Celery. I want to share my approach. I've created an example GitHub repository and wrote step-by-step article.

Please take a look at https://github.com/celery/django-celery-beat with this package you can dynamically define periodic tasks. They are stored in your database, so they are persistent between deployments. I'm using this package with Celery in my project for server uptime monitoring, it is working well. I can dynamically add/delete/update any task.

Something similar is presented in django-celery-beat where you’re able to create schedule for running repeated task. So, there is choice field in admin, and choices are literally names of registered celery tasks.

I would recommend using celery in combination with celery beat scheduling and this package https://github.com/celery/django-celery-beat . What this means is if you have a task that you want to dynamically schedule for different times for different users all you have to do as add a new row to a database table and celery will handle the rest for executing.

If you want more control and/or visibility into your periodic tasks, I'd go with something like Celery Beat, that's easily integrated with Django: https://github.com/celery/django-celery-beat

For me it was django-celery-beat

I use a Django extension called django-celery-beat. It creates several models & one of those models is called crontab. It has a few fields & I would like to add one more field so that I can name these crontabs for easy reference. So I need to override the model & add the field.

The Celery package provides some number of (undocumented!) result backends to store task results in different local, network, and cloud storages. The django-celery-result package adds options to use Django-specific ORM-based result storage, as well as Django-specific cache subsystem.

To keep track of task result

The field is referenced in the docs here: https://github.com/celery/django-celery-results/blob/9b7deb464b0f3fa8c063a1cc70f9fc48829f9793/docs/includes/introduction.txt, and that appears to be accurate, but I don't have any experience with d-c-r personally so I can't really help much more. Hope you figure it out!

Hello, I have been having issues with Django and sending the results of Celery workers. Celery works and produces the results and if I set the backend to the redis server, it works fine. The issue is that Django ORM is not registering the TaskResults. I have tried everything under the sun in regards to configuration and I am sure that it's not the issue. I have found this Github: https://github.com/celery/django-celery-results/issues/102