mark-at-kluster comments

Results 5 comments of


                                            mark-at-kluster

Enabling a cron schedule task will run it immediately if it should have ran while it was disabled

This does not fix it and is unrelated to this PR. The reason this occurs is that tasks are evaluated wether they should be run using the `last_run_at` field. The...

Enabling a cron schedule task will run it immediately if it should have ran while it was disabled

This may be the case for the issue you fixed in your PR, however I don't believe this is the case for this issue. This is because you say `all_as_schedule`...

schedule task

There is no way within the package to stop this happening currently, it appears by design. I outlined how we worked round this issue in #537. Hope that helps!

Tasks fired after changing crontab schedule

see #537

Issue about django-celery-beat and Crontab Expression

This is a duplicate of #537 (or at least the cause is the exactly the same). The reasons this happens is that the crontab expression is evaluated according to when...