18👍
✅
This is most likely the result of scaling your web processes down to zero through the client.
$ heroku ps:scale web=0
Use the heroku ps
command to determine the state of your web processes., and you should take a look at the Error Codes to understand the Heroku functionality.
7👍
I had the exact same problem. At first, when I ran heroku scale web=1
, I got the same ‘Record not found’ error as you. But I waited a few minutes and ran it again, and it worked.
If your build fails on the first push for some reason, then heroku doesn’t automatically give you a web process, and the ‘Record not found’ error might’ve cropped up because something was off with the build at that point.
Source:stackexchange.com