-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heroku restart ignores Scheduled time and starts the task #30
Comments
I'm looking into this. Can you confirm the job type? I've currently fixing an issue w. repeatable jobs where on re-scheduling they can end up re-running the tasks. |
Hi @tom-price , they were "Repeatable Job"s added in django admin, as heroku dynos has a daily restart, at each restart tasks were automatically started ignored their scheduled time. We had to switch to appscheduler+django-rq, no it works as should be, but tasks cannot be managed in admin, we are planning to switch to celery, celery-beat and rabbitmq in near future for stability, better task statistics and flexibility. "where on re-scheduling they can end up re-running the tasks" - yes, looks like it is the problem we had. |
Ahh I see. It do believe PR #34 addresses this issue. |
Heroku has a daily restart for its apps. Our Django-rq-scheduler tasks are starting right after each restart and also at the time that we added. Also, it even starts if enabled field is False.
How to check if it is django-rq-scheduler problem or django-rq or rq?
The text was updated successfully, but these errors were encountered: