alex, i may be extremely green at coding, but i have a very precise thing i need the code to do: run a function periodically on any decided period. so right now im just starting the basic, which is get the fucntion to run everyday at 9. i want to be able to run the same function every 2 days at 5pm for instance
is that the actual end goal here?
at any rate, you should move the scheduling code out of the target function
ok im im doing that now
you can however approximate it with
CronTrigger
(assuming you don't actually mean exactly 24 hour intervals, but 23 or 25 are okay too)
Hello, the scheduler is not working) And I do not know why, the work is carried out in parallel with the asynchronous bot for telegram.
I started the logger, but it also shows that nothing is happening
I started the logger, but it also shows that nothing is happening
make a new function if you need to, and start the scheduler there
asyncio support in apscheduler 3 is a bit iffy
when i add this job, and do the job check
scheduler.add_job(jobstore='default',func=blah1,trigger = 'interval',args=[data,x], id=f'7',start_date=f'{date} 2022-11-30',end_date=f'{date} 2022-11-30',minutes =time,max_instances =5)
on gets_jobs() next_run_time is equal to None
but when i do this
scheduler.add_job(jobstore='default',func=blah1,trigger = 'interval',args=[data,x], id=f'7',start_date='2022-11-30 12:00:00',end_date='2022-11-30 02:00:00',minutes =time,max_instances =5) it shows the jobs next run time
the date in the fstring is actually the time just made an error here
name: 2, trigger: interval[0:15:00], next run: 2022-11-30 17:31:00-08:00, handler: <function blah1 at 0x00000203BA86F640>
name: 1, trigger: interval[0:15:00], next run: None, handler: <function blah at 0x00000203BA894CA0>
I tried it, but it still doesn't work(
Hi, I have a question about how the background scheduler works. Our application either takes commands by CLI or initialise by python API, but it doesn't spin its own event loop or run in the background. If my understanding of the docs is correct, once the CLI script or python instance is closed, the scheduler will close. Is this correct / are there any workarounds to run the scheduler for long periods (e.g. months, years) in a background process, running at startup etc?
5 replies
Hello! Just getting started with APScheduler, and wondering if there's a good way to remove an interval job based off a condition defined in the job. Let's say I'm running a job but completion of the job without errors doesn't mean the job is successful, and I want to run it again. Once some internal logic in the job (perhaps returning True) is satisfied, the job is removed. Is there some sort of pattern that can be used for this? One possibility I was thinking of is raising an exception in the job itself, and using the event listener, but that seems inelegant. Please let me know if I'm missing something! Thanks so much