-
Notifications
You must be signed in to change notification settings - Fork 184
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
apscheduler jobs unexpectedly removed from SCHEDULER_JOBSTORES #119
Comments
hmmm, there is no relation between three jobs. I changed the job's execute time to 5 am but the rest stoped executing at 2 am.. |
Can you show the jobs' configuration? |
These are all the codes in my flask project..
|
Sorry, I couldn't reproduce this issue. |
I've had the same problem, but I use redis as the scheduler_ JOBSTORES。 Redis deleted the ID of the running job. I don't know how to solve it. Please have a look |
I am getting the same issue, i have 56 jobs in my job store and one of the job is getting removed from the job store. I cannot find any solution. |
I have 3 apscheduler jobs in my flask app. Two of them execute every 4 am of the day, the rest executes every hour. The rest job(executes by hour) works well until 4 am next day. (I am not sure if there is any relation between the time when the two execute and the rest one stops.)
The problem is that the job executes by hour will somehow disappear from SCHEDULER_JOBSTORES.
Flask-APScheduler==1.11.0
The text was updated successfully, but these errors were encountered: