@Marvin I've got several flow runs that were scheduled some hours ago but they all appear as late (from 6 to 2 hours late) and nothing is running. We're currently on the free tier but we are still under quota (4.1 of 10 hours used). Any ideas?

It seems the issues you're facing with late runs could be related to scheduling configurations or potential problems with the Prefect Cloud scheduler. Here's a quick summary with links to more in-depth information: 1. If flow runs are marked as Late, it may require manual rescheduling. The Using the Client guide illustrates how to reschedule late flow runs using Prefect's client library. 2. Scheduler settings can impact the timing and execution of scheduled flow runs. The settings include batch sizes and trigger intervals and can be configured as shown in the Schedules documentation. 3. Regarding tiers and limitations, the Pricing page suggests that even on the free tier, you should have all core features, including the scheduler functionality. If you are not exceeding your tier limits (and you mentioned you have only used 4.1 of the 10 hours available), there should not be any quota-based issues affecting your flows. If none of these suggestions or settings configurations address the issue, it might be necessary to check the Prefect Cloud status to see if there are any ongoing incidents or maintenance activities that could affect scheduling. You could also search for any recent GitHub issues about similar problems in the PrefectHQ repository or reach out to Prefect support for more dedicated assistance. To check for any current known issues, you can use the

search_github_issues

function with relevant queries, such as "flow run late", "scheduling problems", or others that pertain to your situation. If you would like to proceed with this, please let me know, and I will perform the search for you.

I tried rescheduling without any luck: they are "late" again. The schedules were working fine and this started happening without any change

It appears that there are some relevant GitHub issues that others have faced with flow runs being "late" or having issues with schedules. Here's what I've found: 1. Prevent running late runs after some threshold: This feature request suggests allowing configuration not to start executing late flow runs after a certain threshold has passed. 2. Multi-select flow runs and set state in bulk (to clear late runs, delete scheduled runs in bulk, and more): This is another feature request to clear late runs more efficiently. 3. Flow runs duplicated when DST ends (v2): An observed behavior where flow runs were duplicated due to the end of Daylight Saving Time. 4. Duplicate flow runs created at end of daylight savings time (v1): Similar to the previous issue, this one pertains to duplicate flow runs being created with Prefect 1.0 when daylight saving time ends. Since none of the open issues seem to specifically address your problem, it might be an unknown or not commonly reported issue. I would suggest raising a new issue in the PrefectHQ/prefect GitHub repository, providing the detailed description of your problem including what you've tried that hasn't worked. It would also be pertinent to include information about your flow configuration, any recent changes, and the environment in which your flows are running. In the meantime, I would recommend you: 1. Verify that the Prefect Cloud platform is fully operational. 2. Check if Daylight Saving Time changes have affected the scheduling of your flows. 3. Ensure that your scheduler settings are properly configured and that there were no unintended changes. If these don't lead to a resolution, contacting Prefect support or the community for additional troubleshooting may be helpful.