Hi,
For Flow deployment - I set concurrency limit ...
# ask-communityk
Karthik Anavarth
03/03/2025, 9:50 AMHi,
For Flow deployment - I set concurrency limit 1 and Collision Strategy ENQUEUE from prefect UI. When I started two flow run for that deployment, the first flow run ran, but the second flow run is still in AwaitingConcurrencySlot status, does it auto start or I have to do something?
b
Bianca Hoch
03/03/2025, 5:12 PMHi Karthik! What version of Prefect are you using? There was a fix released in 3.1.12 which should help with this.
k
Karthik Anavarth
03/04/2025, 4:01 AMI am using prefect==3.0.0, I will upgrade and see thanks
Karthik Anavarth
03/04/2025, 4:01 AMOne more question if I upgrade prefect do i need to deploy the flow gain for it to work?
b
Bianca Hoch
03/04/2025, 2:56 PMNp! I think you'll only need to redeploy if you're using a custom docker image that has an older version of Prefect.
Bianca Hoch
03/04/2025, 2:57 PMOtherwise, you should be good
k
Karthik Anavarth
03/05/2025, 7:05 AMThanks for the help
Karthik Anavarth
03/13/2025, 8:01 AMI upgraded prefect to 3.2.12 and redployed the the flow again still the status is not moved from AwaitingConcurrencySlot
Its a prefect aws ecs worker, I upgraded the prefect version in the docker image, and when i run the flow i can see prefect version as 3.2.12
should i do something with prefect worker pool?
plus1 1
e
Eve Shen
03/13/2025, 7:58 PM@Bianca Hoch I want to +1 on this issue. Here is our question on github https://github.com/PrefectHQ/prefect/issues/17452. Could you please help?
12 Views