Concurrency limit on the second stage of the pipeline is blocking even the first build

I am currently experimenting with the concurrency limit feature. I have tried it on the first stage of my pipeline and it works as expected, with the following builds waiting the completion of the preceding one.
Then I have moved the concurrency limit to the second stage because it would be better for our use case and now it seems broken, even the first build remains in a pending state after completing the first stage.

Any clue?

@Francesco_Zuliani, maybe depends_on would help: Parallelism | Drone ?
Drone calls this β€œgraph execution” when used with multiple pipelines Configuration | Drone

Hi , Please check if the above doc can help , let us know if you face any issues .

hi you can also refer to the below docs :

1 Like

Solved removing the protected mode. Thank you

1 Like