Hi All, We have some flow deployments that run on a cron schedule, with the concurrency limit set to

1

. Lately, some of these deployments are getting cancelled immediately after they get triggered, with a message of

Deployment concurrency limit reached

, even though it does not look like there is a concurrent flow run when this occurs

"validated_state": {
      "type": "CANCELLED",
      "name": "Cancelled",
      "message": "Deployment concurrency limit reached.",
      "timestamp": "2025-09-17T15:50:23.956089+00:00",
      "id": "068cad8b-ff4c-7030-8000-e10f447cbb39"
    }

We bumped the limit to 2 and we were able to kick off the flow run, but we would like to understand why the limit is being reached when it appears no flow deployment is running

hi @Zhibin Dai you likely have an old flow run in RUNNING | PENDING | CANCELLING that is occupying your concurrency slot

No we dont, thats the issue

are you using cloud or OSS

cloud

there was a cloud incident related to this last week, is it possible the active slots state is messed up from that time? i.e. when you say "lately", what timeframe are you talking about?

I think the earliest occurrences were in early Sep. We just manually cleared the problematic slots. Im going to keep an eye on them to see if the issue reappears and i will let you know