Hi - it seems when a flow is registered to Prefect Cloud (v1) with a schedule, then re-registered without a schedule (ie flow.schedule = None), the schedule is preserved server-side and will stick around until manually toggled off via the UI. Is this behaviour intended? If it is, is there a way to override this programatically by explicitly setting an empty schedule of some sort?

Hey @Ryan Sattler!! How are you setting/unsetting the schedule in your flow programmatically? I tried recreating this issue with a simple schedule and re-registering the flow with

schedule=None

and it deleted my schedule in prefect version 1.4.0

hmm, that’s what I was doing but it didn’t work (using/removing a cron schedule). I’m now going to try setting

set_schedule_active = False

What Prefect version are you running?