Skip to content
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.

Sign up for GitHub

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

Jump to bottom

When there is only one task and it is paused, my project raise 'DjangoJob matching query does not exist.' #25

Closed
zhouwe1 opened this issue Jun 12, 2018 · 1 comment
Closed

When there is only one task and it is paused, my project raise 'DjangoJob matching query does not exist.' #25

zhouwe1 opened this issue Jun 12, 2018 · 1 comment

Comments

@zhouwe1
Copy link

zhouwe1 commented Jun 12, 2018

When there is only one task and it is paused, my project raise 'DjangoJob matching query does not exist.'
May be the problem is here:
Now the next_run_time for all jobs is Null, there are several places where next_run_time are needed.
zhouwe1 referenced this issue Jun 12, 2018
@nialllo
Update get_next_run_time to handle Paused jobs
88d9a5a 
Paused jobs have next_run_time of None.

This change makes django_apscheduler.jobstores looks a bit more like apscheduler.jobstores.sqlalchemy which filters out the nulls and picks the earliest next_run_time.
luizribeiro added a commit to luizribeiro/django-sandbox that referenced this issue Jun 17, 2018
@luizribeiro
Downgraded django-apscheduler to 0.2.9 due to jcass77/django-apschedu…
5931217 
…ler#25
@sallyruthstruik
Copy link
Collaborator

Duplicate of #26

@sallyruthstruik sallyruthstruik marked this as a duplicate of #26 Jul 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sallyruthstruik @zhouwe1