Following up on <https://prefect-community.slack.c...
# prefect-community
Following up on 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: We are iterating deployments here:, 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
🙌 1