We have no builds running but the one build I’m trying to run is stuck in the “scheduled” state.
I’ve read some of the past posts on the topic but it seemed to be a temporary issue that was fixed by CircleCI. Anything we can do to fix it now?
1 Like
Turns out that re-running builds which had failed wasn’t working, but pushing a new commit triggered a new build which is running now.
I’m having the same issue today, and pushing a new commit did not resolve it; I still have a build stuck waiting to start, but an empty build queue.
Could you link to a build or paste your config file? It’s possible that you’re configured to use more containers than you have available.