This may not be a bug, but I'm currently using celery==3.1.18 and django-celery==3.1.16 backed by MYSQL and SQS (for queueing) and when I update both attributes or add/remove tasks from CELERYBEAT_SCHEDULE, when the servers get restarted the database tables (/admindjcelery/periodictask/) are not updated to reflect the new code in python. I was wondering if anyone else has seen this - and if I have to manually delete the periodic tasks in django admin to see the new versions get updated/written.
@josephmisiti I too am experiencing this issue. However, I when updating my CELERYBEAT_SCHEDULE options aren't reflected in the Database keyword arguments
This may not be a bug, but I'm currently using
celery==3.1.18
anddjango-celery==3.1.16
backed by MYSQL and SQS (for queueing) and when I update both attributes or add/remove tasks fromCELERYBEAT_SCHEDULE
, when the servers get restarted the database tables (/admindjcelery/periodictask/
) are not updated to reflect the new code in python. I was wondering if anyone else has seen this - and if I have to manually delete the periodic tasks in django admin to see the new versions get updated/written.Thanks!