Following up on https://prefect-community.slack.com/archives/CL09KU1K7/p1651543946765889 I wanted to confirm this was not an issue in Orion. In Orion, we've decoupled the one to many relationship between a Flow and Clocks (technically Schedule has the clocks) that was present with the introduction of a DeploymentSpec, which has a 1-1 with a schedule. Rather than iterating clocks here: https://github.com/PrefectHQ/server/blob/master/src/prefect_server/api/flows.py#L688 https://github.com/PrefectHQ/prefect/blob/cb0f80c6fc743cdae9f2af5b493ed454bc53d07c/src/prefect/schedules/schedules.py#L108 We are iterating deployments here: https://github.com/PrefectHQ/prefect/blob/orion/src/prefect/orion/services/scheduler.py#L83, which have a 1-1 between schedules. To solve the similar case of one flow, parameterized N many times & different schedules, we should be able to create N many DeploymentSpecs for the given flow without scaling issues, correct? cc: @Kevin Kho

Correct, you can create as many deployment specs of the same flow as you wish. Each of them may have a different schedule and may run even on an entirely different infrastructure, depending on flow runner