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
Scheduler don´t run after_success(fuc) after some time. #187
Comments
I have now tested the scheduler for several days. The problem only occurs when I use the SQL repo. I tried to set the SQLalchemy engine to log the queries via echo=true. Unfortunately I get the error message here After using the logs from the DB, I noticed that despite the setting of the id_field with the config: repo=SQLRepo(engine=sec_db_engine, table="scheduler_log", model=MinimalRunRecord, id_field="id") the logs are queryed from the DB using the "created" column. Did i miss something in the config? The documentation mentions that it is better to use an ID column, this may be the issue of the missed runs with after_success(fuc). |
When I start the scheduler, it runs stable for some time, but withouht any msg, the after_success(fuc) stop running.
Only the periodic timer functions are executed.
Screenshots from the DB log
The Scheduler implementation:
The Task implementation
I integrated it along with Fastapi
The text was updated successfully, but these errors were encountered: