Heroku: Your account has reached its concurrent build limit

Question

I'm trying to deploy my app to heroku, currently using the free tier. Over the past 5 days I've been redeploying the app as I made changes. I went overzealous with the deploys and now my app is up to version 35 on heroku under the "activity" tab.

Now the error message in the title prevents me from deploying my app. Google search didn't return a thing. If I have reached the deployment limit how do I delete/free up my concurrent build space?

As of the last few days, I've had a few students who were getting this error message, and I got on their Heroku CLIs and verified there were no builds running on any of their apps. I'm 99% sure that in that case, it's just a Heroku system bug. — JCollier, Aug 31 '22 at 20:34

score 109 · Answer 1 · answered Sep 12 '19 at 15:42

109

For my case, heroku restart worked.

answered Sep 12 '19 at 15:42

Yigit Alparslan

1,377
1
8
13

It restarts all dynos when you do heroku restart. More info: https://devcenter.heroku.com/articles/heroku-cli-commands – Yigit Alparslan May 09 '20 at 19:50

score 72 · Answer 2 · answered Feb 13 '19 at 04:42

72

We can cancel the current build. Or any ongoing build using below

heroku builds:cancel

You can check the list of builds using

heroku builds

Or you can cancel any build using build hash from the above result list.

In case builds command not working, you need to install it using

heroku plugins:install heroku-builds

answered Feb 13 '19 at 04:42

Mukesh Singh Rathaur

12,577
2
23
24

3

I get `Warning: builds is not a heroku command.` with `heroku builds`. Wait, did not read until the end, now I installed the build plugin and it works.. – Timo Feb 06 '22 at 14:00
1

heroku builds:cancel worked for me. – Luccin Sep 02 '22 at 22:01

score 70 · Answer 3 · answered Feb 13 '20 at 19:47

70

I had to try two of these answers back-to-back. Individually, they didn't work for me.

I needed to install heroku-builds with

heroku plugins:install heroku-builds

Then cancel the ongoing build with

heroku builds:cancel

And finally did a heroku restart.

answered Feb 13 '20 at 19:47

lizziepika

3,231
1
14
23

2

This worked for me. Thanks. When you run `heroku builds:cancel` you may get the outout: `Can only cancel pending builds. Build c20a59ad-d093-4c04-bc70-85ec62f1da00 has status 'failed'`, don't panic, just run the `heroku restart` command next, and the build will start. – Promise Preston Feb 12 '21 at 15:57

score 38 · Answer 4 · answered Dec 15 '20 at 17:54

38

Finally, I managed to resolve an issue with the help of the following 3 commands and it works:-

$ heroku plugins:install heroku-builds
$ heroku builds:cancel
$ heroku restart

answered Dec 15 '20 at 17:54

Vikas Dwivedi

5,233
1
21
16

score 13 · Answer 5 · answered Feb 17 '20 at 18:50

13

Try this command from your project directory

heroku restart

answered Feb 17 '20 at 18:50

Sarath Chandran

189
1
7

score 5 · Answer 6 · answered Aug 13 '19 at 22:57

Now you have to verify your account, putting your credit card in Heroku Account.

"Unverified accounts can now run only one build at a time across all their apps. Verifying the account will automatically lift this limit."

see: https://devcenter.heroku.com/changelog-items/1344

score 5 · Answer 7 · answered Nov 29 '20 at 06:29

I managed by mistake to cancele the build in the terminal by ctrl+c, but the build at heroku account was still running.

The correct way is:

If didn't installed earlier:

heroku plugins:install heroku-builds

And then:

heroku builds:cancel -a YOUR_HEROKU_APP_NAME

score 4 · Accepted Answer · answered Oct 31 '17 at 06:23

4

The Heroku said "Engineers are investigating API availability. This may affect Dashboard, CLI commands, builds and other aspects of the platform." I think this is the reason.

answered Oct 31 '17 at 06:23

Bingqiang Wen

88
3

18

still happening 2 years later, though – pythonian 23 Oct 14 '20 at 11:15
12

how about 3 years later – Tafadzwa L Nyamukapa Oct 26 '20 at 14:26
10

how about 3 years and 1 month later – Paulo Roberto Rosa Nov 25 '20 at 22:20
17

How about 3 years, 2 months, 8 days later – Alen Paul Varghese Jan 08 '21 at 07:17
1

we were not here for the Reason. – Lord-shiv Jan 10 '21 at 08:01
2

its happening on 2021 – Yala Yala Herzlin Feb 10 '21 at 01:35
3

How about 3 years, 4 months, 19 Days – Ahmad Anis Mar 19 '21 at 02:52
9

ahaha its been 4 years now – MasterMind Apr 12 '21 at 07:16
3

4 years and 2 months – Piyush Dubey Jun 04 '21 at 07:55
2

I guess that makes this 4 years and 3 months then – ploopploop Jul 08 '21 at 11:37
3

Reached 4 years and 4 months. – SAL Aug 05 '21 at 19:01
2

how about 4 years and 10 months – Subham Chakraborty Jan 10 '22 at 08:15
The real answer: https://stackoverflow.com/a/57910276/8659405 – J.R. Bob Dobbs Mar 13 '22 at 17:16
This answer shouldn't have been accepted, there are many other answers with the correct solutions. – Daniyal Malik Aug 14 '22 at 10:22

score 4 · Answer 9 · answered Jul 29 '22 at 07:54

4

This helped me "Restart all dynos"

answered Jul 29 '22 at 07:54

atazmin

4,757
1
32
23

score 1 · Answer 10 · edited Jun 20 '20 at 09:12

1

Try to:

Try to check https://devcenter.heroku.com/changelog-items/1344 for important logs
Try to reinstall your app(%65 works)
Try to create a new account(%100 works)

edited Jun 20 '20 at 09:12

Community

1
1

answered Jan 01 '20 at 19:54

score 0 · Answer 11 · answered Jul 01 '22 at 16:33

Pushing too many time a day to GitHub with auto redeploy will result to this error. The simplest solution is to delete your app on Heroku, create a new one and redeploy. Make sure your commit to GitHub has "Node" and "NPM" or "YARN" versions specified within the engines parameter in your package.json file.

Deleting and redeploying is the easiest bypass.

I don't think you need to verify your account using your credit/debit card. Especially on a personal account. Scope include minimum viable products (MVPs), personal projects or proof of concepts.

`

"name": "app name",

"version": "1.1.0",

"private": true or false,

 "engines": {

  "node": "16.14.0",

  "npm": "8.3.1"

},

`

score -1 · Answer 12 · answered Jan 23 '22 at 16:18

This also happens if you have your repo connected and set to auto-deploy.

I had this issue since I had just updated my repo, heroku had started a build already. So when you tell it to build there's already a build going on.

The solution is just to wait until the build finishes, or at least that solved it for me.

score -2 · Answer 13 · answered Aug 30 '21 at 18:39

-2

If you are a little noob like me who just ran out of all deploys available. Just create a new app and the problem is then solved! Simple!

answered Aug 30 '21 at 18:39

Jaydeep Dholakia

187
2
5

Heroku: Your account has reached its concurrent build limit

13 Answers13

Try to:

Linked