Dan Cabrol
05/04/2024, 3:04 PMMarvin
05/04/2024, 3:04 PMactive
flag of the deployment through the API or the UI manually or programmatically to disable and enable the schedule. This can be automated by a separate process that monitors flow runs and toggles the active
state of the deployment after a successful run.
3. Custom Scheduler Logic: Create a custom script that interacts with the Prefect API to schedule flow runs dynamically, rather than relying on a cron schedule. This script could schedule the next flow run for the following day after a successful run.
The important links here are Schedules in Prefect which could help understand how schedules can be activated or deactivated and Using the Prefect Client, which shows how to programmatically interact with flow runs.
For a more detailed solution tailored to Prefect 2.x, we might dive into the documentation further or examine recent user strategies on GitHub issues.
Would you like me to look for specific examples or commands that may assist in solving this?