it seems that by not setting an environment the default envi

Question

it seems that by not setting an environment the default environment is used The default environment loads the default executor which is the localExecutor which the docs say gt An executor that runs all functions synchronously and immediately in the main thread To be used mainly for debugging purposes

Chris K. · Answer

still I have 3 parallell flow runs

Chris K. · Answer

with ```flow executor = LocalDaskExecutor scheduler= threads num workers=1 ```

Kevin Kho · Answer

The executor is for a flow run Not across flow runs So each of those Flows has an executor

Kevin Kho · Answer

Prefect Cloud has <https docs prefect io orchestration flow runs concurrency limits html|Flow Run Concurrency > limits which is a separate thing if you need it

Chris K. · Answer

I m running the flows each of the 3 is the same flow file registered via graphql the Ui Run button

Chris K. · Answer

so you are saying I cannot limit the amount of flows an agent is processing in parrallel in OS prefect

Kevin Kho · Answer

The concurrency limit is not on the agent level It s on a Flow level If you are using Server you need to write additional <https github com PrefectHQ server issues 307|code> because Server doesn t have the concurrency limiting

Kevin Kho · Answer

One flow can have multiple invocations flow runs This is desirable when you have like multiple parameter sets you want to run concurrently

Chris K. · Answer

ok thank you this is already 90 of what I want I guess where is this code going inside prefect core I guess instead of canceling I m able to re schedule the runs take arount 15 min so I could re schedule and then check again for how I understand this

Kevin Kho · Answer

That code snippet would go in the Flow definition It utilizes flow <https docs prefect io core concepts notifications html state handlers|state handler>

Kevin Kho · Answer

Yes you can do that

Chris K. · Answer

perfect thank you for taking the time to point me to this

Kevin Kho · Answer

Ah well You need to do both cancel the current and re schedule the next in the same state handler

Kevin Kho · Answer

Of course

Chris K. · Answer

btw state paused has this gt `start time datetime ` time at which the task is scheduled to resume defaults to 10 years from now if not provided

Chris K. · Answer

should be Cancel + Schedule in once from my understanding

Kevin Kho · Answer

I saw your response on the Github issue Good catch and thanks for mentioning