[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Help](/c/help/9) # Why Vercel deployments stop triggering after reaching Hobby plan limits 1 view · 0 likes · 8 posts Smartcomprasmx Tech (@smartcomprasmx-tech) · 2026-04-10 ## Problem My project stopped triggering automatic deployments from GitHub today. After investigation with Vercel support chat, we believe the daily deployment limit was reached due to multiple reconnection attempts and manual redeployments while troubleshooting a webhook issue. ## Current Behavior * New commits to `main` do not trigger deployments. * Manual redeployments also fail silently. * All deployments show **Commit: `ee0d034`** regardless of newer commits on `main`. ## Expected Behavior * New commits to `main` should trigger automatic deployments. * The most recent commit on `main` is `3774ff4` and should be deployed. ## Steps that led to this 1. Webhook stopped working 2. Reconnected Git repository multiple times 3. Uninstalled and reinstalled Vercel GitHub App 4. Each attempt counted toward deployment limit 5. Now limit is reached and no deployments trigger ## Environment * **Project URL:** cuanto.com.mx * **Repository:** `smartcomprasmx-tech/cuanto-mx` * **Framework:** `Vite` + `React` * **Plan:** `Hobby` Update: 12:03am the issue persists. New commits are still not triggering automatic deployments. I pushed a test commit after midnight and Vercel still clones commit `ee0d034`. This confirms it's not just a daily limit issue — the GitHub webhook is not working properly. Please check the webhook configuration for project `smartcomprasmx-tech/cuanto-mx`. Thank you. Pauline P. Narvas (@pawlean) · 2026-04-11 What's the case number you shared with support? Happy to take a look! You should also update the case with the new update you shared :slight_smile: Smartcomprasmx Tech (@smartcomprasmx-tech) · 2026-04-11 Hi, I don't have a case number… I'm on the Hobby plan and i was redirected to the community support. The issue is: GitHub webhook is not triggering automatic deployments for project `smartcomprasmx-tech/cuanto-mx`. All deployments show commit `ee0d034` regardless of newer commits on main. I have tried reconnecting the repository and reinstalling the GitHub App multiple times. Thanks Smartcomprasmx Tech (@smartcomprasmx-tech) · 2026-04-11 update: I tested the Deploy Hook manually and it returns `{"job":{"state":"PENDING"}}` but no deployment appears in the dashboard. The job is created but never processed. GitHub Actions workflow also ran successfully and called the hook, but no deployment was triggered. Deployments are being created as PENDING but never executed. Pauline P. Narvas (@pawlean) · 2026-04-11 Could you perhaps try this? https://community.vercel.com/t/vercel-deployment-blocked-because-commit-author-does-not-have-contributing-access/36381/9?u=pawlean Smartcomprasmx Tech (@smartcomprasmx-tech) · 2026-04-11 I re-authenticated my GitHub account in vercel.com/account/settings/authentication but the issue persists. New commits still don't trigger deployments. Deploy Hook returns PENDING but no deployment is created. The latest deployment still shows commit `ee0d034` Smartcomprasmx Tech (@smartcomprasmx-tech) · 2026-04-11 update: 1. GitHub Actions workflow runs successfully and calls the hook 2. Last job ID: Zded8Qt0FVEh58Bw59Wb 3. All recent deployments stuck on commit ee0d034 4. Tried: reconnecting repo, reinstalling GitHub App, re-authenticating, new Deploy Hook, GitHub Actions 5. No env secrets in vercel.json 6. Personal GitHub account (not organization) 7. Project: smartcomprasmx-tech/cuanto-mx 8. Plan: Hobby (not a organization) Could you please check the internal logs for job ID `Zded8Qt0FVEh58Bw59Wb`? please in other case i saw : Vercel staff found the error 'deployment is blocked due to insufficient permissions… github user not part of team'. i suspect something similar is happening with my project Smartcomprasmx Tech (@smartcomprasmx-tech) · 2026-04-12 Resolved. The issue was fixed by creating a new Vercel project importing the same repository. The new project correctly picks up new commits automatically. Thank you for your time