apscheduler was stuck after it ran to“apscheduler .scheduler - DEBUG - Looking for jobs to run“

[whuhyk]

Things to check first

• [X] I have checked that my issue does not already have a solution in the FAQ

• [X] I have searched the existing issues and didn't find my bug already reported there

• [X] I have checked that my bug is still present in the latest release

Version

3.10.4

What happened?

I deployed the flask_apscheduler with waitress-serve. After a day, it seems it does not work and stuck in “apscheduler .scheduler - DEBUG - Looking for jobs to run“. When I request the flask_apscheduler api,the log writes as this:

2024-01-06 08:30:00,004 - apscheduler.scheduler - DEBUG - Looking for jobs to run 2024-01-06 08:58:34,033 - waitress.queue - WARNING - Task queue depth is 1 2024-01-06 09:01:19,415 - waitress.queue - WARNING - Task queue depth is 2 2024-01-06 09:02:39,501 - waitress.queue - WARNING - Task queue depth is 3 2024-01-06 09:03:16,200 - waitress.queue - WARNING - Task queue depth is 4 2024-01-06 09:15:20,963 - waitress.queue - WARNING - Task queue depth is 5 2024-01-06 09:24:41,826 - waitress.queue - WARNING - Task queue depth is 6

How can we reproduce the bug?

from dq_app import create_app from waitress import serve

app = create_app() if name == 'main':

app.run('127.0.0.1',5000)

serve(app,host='127.0.0.1',port=5000)

[agronholm]

That doesn't run for me: ModuleNotFoundError: No module named 'dq_app'.

[agronholm]

Closing due to lack of responses.