Why no effect after setting misfire_grace_time to None? #1047
Unanswered
GusarevKirill
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I use APScheduler 3.11 in my project.
Everything was fine with my app on Windows during development. But when I made a Docker image with my app and started a container, I got an error
Run time of job "Manager._search_job (trigger: interval[0:01:00], next run at: 2025-04-28 19:02:04 UTC)" was missed by 0:00:01.807009. This error appears almost on every call of the job. Only ~~10% of job calls was successful.I tried to add
misfire_grace_timeparameter (misfire_grace_time=None,misfire_grace_time=9999, etc.) to.add_jobmethod, but it didn't have any effect.The piece of code that registers this job:
What am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions