Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

image.png

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. Anyone have any idea why or how I might debug it? If relevant, I'm running on static infra on GCP using `serve(<http://flow.to|flow.to>_deployment())`

Maybe it is because of that message about the work queue not having any active workers? But I thought I didn't even really need work pools and queues with static polling?

hi <@U07VDFKCF3L> - do you happen to have a CI job that runs `prefect deploy` or otherwise creates / updates deployments with an active schedule?

Ok I think it is when I restart the container

Here's the code that sets the schedule
```    serve(
        echo_flow.to_deployment(name="echo_flow", work_pool_name="ringmaster-pool-3"),
        run_weekly_ringmaster.to_deployment(name="ringmaster-mon-thu", work_pool_name="ringmaster-pool-3", schedules=[CronSchedule(cron="0 17 * * 1-4", timezone="America/Los_Angeles")], parameters={"test_send": False, "short": True}),
        run_weekly_ringmaster.to_deployment(name="ringmaster-fri", work_pool_name="ringmaster-pool-3", schedules=[CronSchedule(cron="0 17 * * 5", timezone="America/Los_Angeles")], parameters={"test_send": False, "short": False}),
        run_single_call_ringmaster.to_deployment(name="ringmaster-single", work_pool_name="ringmaster-pool-3")
    )```

Is there another parameter needed to enable the schedules?

Hey <@U07VDFKCF3L>, based on what I'm seeing in <https://prefect-python-sdk-docs.netlify.app/prefect/cli/flow/?h=serve#prefect.cli.flow.serve|the docs for serve> this feels like a bug. Can you open an issue with a minimal reproducible example?