Concurrency Limit message with no active builds

Hi All,

Are there any undocumented build limit criteria? I have one build (managed workflow, submitted with eas-cli 0.57.0), which is waiting to join queue because I’ve reached my concurrency limit, even though I have no other builds running.

Are there any other criteria for this status that I may have inadvertently triggered?

I’ve tried cancelling and re-submitting the build, but the same thing happenes. Also checked previous builds to ensure they’re all finished.

Cheers!

Thank you for reaching out about this. There are no other criteria, the build should have been queued right away. A technical issue prevented this from happening.

We have manually corrected this, and your build is now processing. Apologies for the inconvenience.

Wonderful :), Thanks!