Lukas Dobler

Yes sure, in my case they should add a new schedule with the same name at the end of the task. I referred to the non existence of the new...

I was able to reproduce this bug also with 4.0.0a3. Posting my example now. Just a quick comment: if you use `await scheduler.add_job(create_schedules)` you get directly the error with the...

I upgraded apscheduler, deleted the old tables in the database and tried to use the same code as before, but getting now this error: ``` 2023-11-13 08:17:24,598:ERROR-bug_demo:hon3.10/site-packages/apscheduler/_schedulers/async_.py", line 737, in...

The error is from the Interval trigger, just create a schedule with an interval trigger. It executes ones and then creates this error

I created a whole new database and run the standalone example, which works fine for me! I then cleared the whole database and used my code again. Still getting the...

Replied there as well. For me it was more debugging, to understand what arguments are going in. I checked my initial report by the way with the pickle serializer and...

And I think I found the problem causing this bug of the disappearing schedules. My example code to reproduce it creates 2000 times the same schedules and numerating them. It...

Schedule 1 with a datetrigger is executed, during the execution a new schedule 2 with the same id is created. Sometimes during the execution of the job of schedule 1,...

As long as it is consistent I am okay with either one. I would prefer it not being available unless it produces another runtime. Because the schedule exhausted and therefore...

This out of the way, the initial reported error still occurs 🙈 During that I also stumbled across another thing: How does apscheduler handle many pending jobs in combination with...