@Marvin I am using a severless push workpool. Is there any way to make sure only x amount of workers are run at the same time while the other jobs wait for execution ?

In Prefect, push work pools allow Prefect Cloud to submit flow runs for execution to serverless computing infrastructure without running a worker. They currently support execution in GCP Cloud Run Jobs, Azure Container Instances, and AWS ECS Tasks. You can create a push work pool that sends work to these services. However, the order in which flow runs are submitted for execution is determined by priority. If all flow runs are capable of being executed with no limitation due to concurrency or otherwise, priority is still used to determine the order of submission, but there is no impact on execution. If not all flow runs can be executed, usually as a result of concurrency limits, priority is used to determine which queue. For more detailed information, you can refer to the following documents: - Push Work to Serverless Computing Infrastructure - Work Pools Please note that the documents might not directly answer your question about limiting the number of workers at the same time while other jobs wait for execution. It's recommended to reach out to the Prefect community or support for more specific guidance on this topic.

you should be able to set a concurrency limit on your push work pool

Thanks! I assumed it was not possible : https://docs.prefect.io/latest/guides/deployment/push-work-pools/ . Am I reading the docs wrong or are they dated?

oh, i might be mistaken! i quickly checked on mobile :/ sorry about that. i may have fooled myself looking at our sandbox workspace

Well i tested it and it works, so i guess the docs are probably wrong?

that’s possible - i will check on this when we return from holiday - thanks for the update!

Hi Nate, the concurrency setting no longer works for the push pool now. I get this message:

Response: {'detail': 'Push pool concurrency limits cannot be set.'}

Has it been patched somehow?

hey @Adam - we are planning to implement push pool concurrency soon!

That would be amazing, is there any estimated timeline please?

I'm sorry, i don't have a timeline to share right now. I'm not working on the feature myself, but I'd be hopeful that it would exist by the end of the year, but wouldnt say for certain