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

I noticed after upgrading to prefect 0.15.5 that the argument `set_schedule_active` is now defaulted to `True` (use to be `False` i believe) which causes a warning if you register your flow without a schedule in the prefect UI. I was wondering if this was intended as I didn't see anything about this change in the release notes.

Hey Kathryn, I don't think this default has changed in the `Client` <https://github.com/PrefectHQ/prefect/blame/5221e6c4ef68eb8c7659c212ea937d1856cee8a4/src/prefect/client/client.py#L1042>

Nor does the batch registration PR look to touch the call here to `register` <https://github.com/PrefectHQ/prefect/pull/4930/files>

So that’s related to <https://github.com/PrefectHQ/prefect/pull/4930#issue-725075932|this> PR where flows with no schedules will have their scheduled turned on but we’ll be addressing this in the backend of Prefect Cloud.

Got it, thanks <@U01QEJ9PP53> and <@U01CEUST9B5>