Actions concurrency bug report

I tried to implement the new concurrency feature in actions today and encountered a bug. We have 10 web scrapers running as 10 separate workflows here. I set them to the same concurrency namespace and lined up the crontab times so they’d all start at the same time. My hope is that they would run one by one. What I found is that it appears to have lined up pending tasks, but never triggered the followup actions after the first one finished.

1 Like

Thanks for reporting! We have identified a bug and we are pushing out a fix for that.

Releasing permits is not quite working across workflows, if it’s the same workflow it would work as expected. Once the fix is out, it would work in your scenario as well, we will circle back when it’s out (mid next week).

3 Likes

Thank you for the rapid response. I appreciate that this is a beta feature and that it’s going to great once the early bugs are ironed out.

1 Like

I believe this should be fixed, please let us know if you face any problems! We would suggest using new concurrency key, as the old one where you faced issues might have some backlog and probably won’t work as expected

3 Likes