@Marvin When an deployment gets kicked off to a pool with two agents, both agents should be able to do the deployment whenever there are concurrent tasks in the deploy right? For some reason I have a job with 100 concurrent tasks and 10 agents, but only 1 agent is doing the work right now

It seems that there's some confusion around agents and workers in Prefect's new deployment model. According to the Prefect documentation, agents are part of the block-based deployment model, and it is now recommended to use workers instead. Workers are responsible for executing flow runs and are part of Work Pools, which simplify the specification of a flow's infrastructure and runtime environment. Multiple worker processes can be started for a single work pool, and workers can obtain scheduled work from the work pool to execute flow runs. If you're experiencing an issue where 100 concurrent tasks are running but only 1 agent is doing the work, it might be related to the transition from agents to workers and the configuration of your work pool. You should ensure that your work pool is properly set up to allow multiple workers to execute tasks concurrently. To address this situation, you can either review the Prefect documentation on workers and work pools or search for relevant discussions or issues on GitHub. Since you mentioned that you have 10 agents instead of workers, this could be the root of the problem because Prefect has moved towards a model that prefers workers over agents. You might want to consider transitioning to the new worker-based model for more efficient concurrent task execution. If you need detailed guidance on how to migrate from agents to workers or how to optimize your configuration, please consult the Prefect documentation or provide more details about your current setup.