-
Notifications
You must be signed in to change notification settings - Fork 97
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
Logging of job execution fails if the job is no longer available in the job store #116
Comments
Could you please provide the full stack traceback for this exception so that we can identify the root cause? It looks like the job is scheduled to run immediately, and to execute exactly once? It is possible that APScheduler could have removed the job from the job store already by the time that we try to log that single execution in the |
Error notifying listener During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): Error notifying listener During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Describe the bug / feature
django==3.1.2
django-apscheduler==0.4.2
database:postgresql 10.0
This is my class view
`
class LoginView(View):
`
and error
django.db.utils.IntegrityError: insert or update on table "django_apscheduler_djangojobexecution" violates foreign key constraint "django_apscheduler_djangojobexecution_job_id_daf5090a_fk" DETAIL: Key (job_id)=(shadow1) is not present in table "django_apscheduler_djangojob".
The text was updated successfully, but these errors were encountered: