Open claymation opened 13 years ago
Interesting, I imagine we have to add another field marking it as "merged from defined tasks", and then check those to verify that the defined tasks still exists.
I am currently experience the same problem on django-celery==3.2.1
.
Was this fixed or it's a known issue?
I tried 3.3.1
and the problem still persists.
When using djcelery.schedulers.DatabaseScheduler:
This also happens when removing periodic tasks—the database entries persist after the tasks no longer exist in code.