Hello, I have a question regardin schedules & deployments, i can have a deployment and i can run it as custom run as much as i want, i can even setup automation to run it on event But one thing is bothering me, why can i use my deployment (one deployment) to schedule 2 different schedules with different params, so i can create one deployment and use more schedules with different params on it ?

Hello, A deployment is a flow with params including the scheduling. What you can do i reuse a certain flow but deploy it for each schedule you want with certain params, even different names (daily, weekly) Do you think there is an issue with that ?

well if i can use one deployment to run at same time few flows, why can't i use one deployment for more schedules? why would i need to deploy same thing multiple times so i could have more schedules on it?

That’s just not how Deployment is designed. You are not deploying the same thing since schedule and params are different. It’s like saying objects are the same because the are from the same class. If that’s a no go for you, maybe prefect is the right tool for the job 😅

but i already di that, just with webhook and automation I can create automated hits on webhooks at certain times, with paramas that are passed to deployment for custom run each time and in that way i have multiple schedules per deployment with dxifferent arguments

I know you can do it, but I guess I don’t see a reason to go through the trouble of implementing such a solution rather than have several deployments that are easier to monitor and visually show in the interface

well if each run is different run, how does that complicate anything? U see flows, u see flow** (errors/logs u can add custom naming Whole deal is about 1 deployment that can run XYZ times at the same time, customization to run with same paramas, and yet u cant have 2 schedules flow runs **

All I’m trying to say it that it’s a matter of opinion. You might think your idea is the best way of doing it but Prefect implements it differently and personally I think it makes more sense the way they designed it. If don’t want to adapt to the logic behind it, it’s ok you can keep your Webhooks and Automation and ask for the feature but if I’m not sure they would implement it.

Im trying to find a way to do this without webhooks, since i have to setup them on serveri, my idea was to do most of chores on cloud, so i could directly use existing deploys to schedule various reports

That’s what i’m trying to say here. You can do what you’re asking using multiple deployments. If you don’t want to use prefect logic, you will have to use external ressources to achieve your goals

having multiple schedules on one deployment is actually something we're working on right now!

Great news then 😄 Will the params also be allowed to change with the schedules ?

Just multiple schedules for now!