I have 2 projects in Hobby plan. These are a frontend project built with React and Vite and a backend built with nodejs and Express. I have both github projects connected properly and, in the past, I’ve been triggering different deploys using Deploy Hooks in both projects. Actually, both projects are deployed right now in the following URLs:
The point is that after a few months without doing updates, I’ve tried to trigger new deploys after merging some changes on both projects and suddenly they don’t work anymore. I’m able to trigger the deploy (supposedly) since I receive a response from the HTTP request to the hook which is the following:
But, as you can see, the state is PENDING and it won’t move from there. The behavior is exactly the same in both projects so now I’m stuck with no option to upgrade my software and I need to do so for my clients.
Has anyone experienced the same problem? Any ideas on where the problem might be? As I’m in Hobby plan Vercel gives no support and they don’t answer my questions, but I would say it is a problem on their end and the AI chat is unable to do anything to help.
It sounds like you’re probably running into the concurrent build limit on the Hobby plan. Since both of your projects are trying to deploy and getting stuck in a PENDING state, this is usually the culprit.
You only get one concurrent build
If a build is already running (or gets stuck), anything after that will just sit in PENDING
How to fix it →
Check your Vercel Dashboard and look for any builds that are still running or stuck
Cancel anything that’s stuck so the queue can clear
Deploy one project at a time and don’t trigger both deploy hooks at once on the Hobby plan
Once the stuck build clears, the other deployments should move again.
Let me know what you see in the dashboard and I can help you troubleshoot further!
Thanks for your response. I’ve checked that, just in case, but I’m afraid there’s no jobs i the queue. Actually, I’ve tried to redeploy the previous deployment in one of the projects which if, as you mentioned the plan has already any other job stuck in the queue it shouldn’t be able to redeploy. However, the redeploy worked as expected and performed the build and deploy successfully.
Also, another thing is that when I hit the redeploy button, in the deployments list it appears first as Queued and later as Ready. However, the deploys made via Deploy Hook, even if they appear to be created and Queued (as per the PENDING status shows), I can’t see them in the list so, again. I think it exists some kind of problem on Vercel side, because somehow it’s unable to link the pendind deployments with the project itself.
Adding some info, I’ve also tried to remove the existing hook (just in case it existed some kind of expiring date or similar and created a brand new one to check if that was the problem and the behavior with the new hooks have been exactly the same)