Crontab Jobs being run twice at expected time about redbeat HOT 4 CLOSED

Further - it appears you can work around the issue by entering a job, allowing it to run once, then changing the parameters and it will run in the schedule as requested after that. As long as the name is the same its treated as the same job.

Also setting app.conf.CELERY_ALWAYS_EAGER=False will also prevent jobs from overwhelming the queue on a restart next time.

from redbeat.

This seems to be the same as issue #79

from redbeat.

Yup, it sure is the same issue. I was trying to dig into the code a bit to try to figure out what exactly the RedisScheduler looks at during the initial run, but its not obvious to me (yet). This project does 90% of what I need it to even in this state as I can for now just set interval timing on jobs (every 23 hours or something vs exact time). I will try to work around this and hope the author can look into the issue a bit more. Easy dynamic scheduling of large regularly occurring jobs is my goal with some ability to add and subtract from a web interface as needed.

from redbeat.

I'm closing this as a duplicate of #79, there is additional information available in that issue.

from redbeat.