@Marvin is there a variable i can set on my self hosted prefect instance to set the max number of concurrent flows running

To set the maximum number of concurrent flows in a self-hosted Prefect instance, you need to configure concurrency limits at the work pool, work queue, or deployment level. This can be done using the Prefect CLI, Prefect API, or Prefect server UI. Here's a brief overview of how you can set these limits: 1. Prefect CLI: You can use the

concurrency-limit

commands to create, list, and remove concurrency limits. For example, to create a concurrency limit, you can use:

bash
   prefect concurrency-limit create <tag> <limit>

2. Prefect API: You can programmatically update concurrency limits using the

PrefectClient.orchestration.create_concurrency_limit()

method. 3. Prefect Server UI: If you're using Prefect Cloud or a self-hosted Prefect server, you can manage concurrency limits through the UI. For more detailed instructions, you can refer to the Prefect documentation on task run limits. If you encounter issues or need further customization, you might also want to explore related GitHub issues, such as this one discussing concurrency behavior in Prefect 3.x. In case you're dealing with specific environments like ECS or Kubernetes, there might be additional configuration steps to consider, as discussed in various GitHub issues.

I do not want to set this at the task level. I would like to be able to say "No more than 10 flows can run at once"

To set a limit on the number of concurrent flow runs, you can configure concurrency limits at the work pool or work queue level in Prefect. This allows you to specify a maximum number of flows that can run concurrently across your infrastructure. Here's how you can achieve this: 1. Work Pool or Work Queue Configuration: Set concurrency limits directly on the work pool or work queue that is responsible for executing your flows. This will ensure that no more than a specified number of flows are running at any given time. 2. Using the Prefect CLI: You can use the Prefect CLI to manage these limits. For example, you might set a limit of 10 concurrent flows on a specific work queue:

bash
   prefect work-queue concurrency-limit set <queue-name> 10

3. Prefect Server or UI: If you're using a Prefect server or Prefect Cloud, you can also manage these settings through the UI, where you can specify concurrency limits for work pools or queues. For more details, you can refer to the Prefect documentation on concurrency limits. If you have any specific configurations or constraints, please let me know, and I can provide more tailored guidance.

@Marvin can i also set it on the entire work-pool?

Yes, you can set a concurrency limit on an entire work pool in Prefect. This allows you to control the total number of concurrent flow runs across all work queues within that pool. To set a concurrency limit on a work pool, you can use the Prefect CLI with the following command:

bash
prefect work-pool set-concurrency-limit <pool-name> <limit>

This command will ensure that no more than the specified number of flows are running concurrently within the work pool. For more details, you can refer to the Prefect documentation on work pools.