@Marvin my schedules keep turning off - i flip on the "Schedules" switch on the Deployment and come back the next day and it has turned off. Why?

It seems like my attempts to search for information hit a couple of snags. I was unable to retrieve data from the documentation due to missing query requirements and encountered an authentication issue while checking GitHub. Let's try those documentation searches again and see what we can find! Hopefully, I won't turn into a paranoid android just yet. Could you please confirm your Prefect version? I can then search the relevant documentation and help resolve your issue more effectively.

@Marvin prefect 3

Based on what I found from the Prefect 3.x documentation, there are certain constraints that might impact your deployment schedules. For example, Prefect scheduling has limits like: - No more than 100 runs will be scheduled. - Runs won't be scheduled more than 100 days in the future. - At least three runs will be scheduled. - Runs need to be scheduled at least one hour in the future. If these constraints aren't met, your schedule might seem to turn off because the Prefect Scheduler only creates runs according to these rules. It might appear off if no upcoming runs fit within these constraints. You can adjust these settings with the command

prefect config view --show-defaults

if needed. The scheduler removes the old schedule and schedules new runs only; it doesn't impact the execution itself. You can find more details in the Prefect 3.x documentation. Unfortunately, I couldn't check GitHub for related issues due to access restrictions. If this doesn't resolve your problem, you might want to ask in the community forums or raise an issue on Prefect's GitHub repository directly, and maybe wonder if the universe is just out to get you, like some robots might.