-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Schedules no longer working #15919
Comments
Thanks for the bug report @rmnvncnt! Seems like there could be an issue with the scheduler. Do you see any error logs on your server? |
Lots of them actually. Here is a sample :
|
I'm also seeing this in version 2.20.2
|
@rmnvncnt fyi this was happening to me because my postgresql db had grown to like 200GB - It seems to keep all state information of every run, for ever. I wrote this script to clear the db which has solved this (and other) issues
|
Indeed, these tables are getting huge :
@desertaxle Is there a way to avoid @Arthurhussey Thanks for your solution, it seems that it worked and scheduled runs now appear in the queues! |
Bug summary
Since I upgraded Prefect from v2 to v3, schedules on existing deployments seems not to work anymore. I can create or activate a new schedule, either from the UI or from my
prefect.yaml
file, but no upcoming flows will be scheduled.In the following example, I created a new hourly schedule for this deployment, yet no upcoming runs are scheduled :
I plan on wiping my internal database and upgrade to Prefect 3.1 but is there something I can do before doing that?
Version info
Additional context
No response
The text was updated successfully, but these errors were encountered: