Closed pi5 closed 10 years ago
When the scanscheduler is running, the remove operation does not remove the complete document from the "scanschedule" collection. Fields specific to the scheduler are kept intact which include "_id", "last_run_at" and "total_run_count"
On remove operation, the "_id", "last_run_at" and "total_run_count" are still present in the document in mongodb.
This causes the celerybeat-mongo to throw an exception: Exception("must define internal or crontab schedule")